Development

[jordanlambrecht]

No description provided.

[github-actions]

Knip Code Analysis

Found 8 total issues

Category	Count
Unused Dependencies	1
Unused Dev Dependencies	3
Unused Exports	4

View details

Run pnpm knip locally to see the full report.

Use pnpm knip:filter pattern to filter results by file path.

---

Use /** @public */ JSDoc tags to mark intentionally exported symbols.

[github-actions]

✅ Security audit passed

Passed (38/38)

• ✅ Auth enforcement on protected routes (per-handler)
• ✅ No dangerous functions (eval, innerHTML, etc.)
• ✅ No hardcoded secrets in source
• ✅ Security headers in next.config.ts
• ✅ Cookie security (httpOnly, sameSite, secure)
• ✅ No sensitive fields in API responses
• ✅ No .env files committed to repo
• ✅ No raw SQL in API routes
• ✅ No fetch/redirect with unvalidated URLs in routes
• ✅ Timing-safe comparison for secret values
• ✅ No raw SQL migration files (schema-first only)
• ✅ External fetch calls have timeouts
• ✅ Docker container runs as non-root user
• ✅ Public routes match proxy allowlist
• ✅ File delete operations have path traversal defense
• ✅ Password hashing uses Argon2 (not SHA-256/bcrypt)
• ✅ Encrypted columns written via encrypt()
• ✅ TOTP 2FA flow integrity
• ✅ Emergency lockdown flow integrity
• ✅ Scrub & delete (nuke) flow integrity
• ✅ Backup restore flow integrity
• ✅ Login flow integrity
• ✅ Auth result checked before proceeding
• ✅ Backup password inputs bounded before key derivation
• ✅ Webhook delivery fetch uses redirect: "error"
• ✅ SESSION_SECRET minimum-length guard in auth/crypto modules
• ✅ Notification URL validators include SSRF protection
• ✅ Dockerfile does not COPY sensitive files
• ✅ No secret env vars in client components
• ✅ Adapter Cookie headers guard against injection
• ✅ Adapter files do not log credential values
• ✅ No console.log in API routes
• ✅ No TODO/FIXME in security-critical files
• ✅ JSON.parse wrapped in try-catch
• ✅ No swallowed errors in catch blocks
• ✅ Request body size validation on upload routes
• ✅ BigInt fields use string serialization
• ✅ No raw error messages in API responses

---

Summary: 38/38 checks passed

See scripts/security-audit.ts for check definitions and SECURITY.md for the full security architecture.

[Copilot]

Pull request overview

This PR updates JavaScript/TypeScript dependencies for the project’s Next-based app and its tooling, refreshing the lockfile accordingly.

Changes:

• Bump @tanstack/react-query to ^5.99.0.
• Update next from 16.2.2 to ^16.2.3 (also changing from a pinned version to a caret range).
• Bump dev tooling deps (dotenv, knip) and refresh pnpm-lock.yaml with updated transitive versions.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updates direct dependency specifiers for React Query, Next, dotenv, and knip.
pnpm-lock.yaml	Updates resolved versions/integrity entries and adds/remaps transitive dependencies to match the new specifiers.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

[Copilot]

Changing next from an exact version to a caret range makes fresh installs (or any non---frozen-lockfile install) able to pick up newer 16.x minors/patches without an explicit PR, which can introduce behavior changes in a core runtime dependency. If the intent is to keep framework/runtime versions stable (similar to react/react-dom being pinned), consider keeping next pinned to an exact version (or otherwise document why next is allowed to float while react is pinned).

Suggested change

	"next": "^16.2.3",
	"next": "16.2.3",