fix(security): patch Next and OpenTelemetry dependencies with CI gates
This commit is contained in:
1 parent
1a602551ad
commit
752d243ae8
29 files changed
+1138
-9280
No files matched your search
@@ -6,3 +6,4 @@
|
||||
| [MINIFEST.md](MINIFEST.md) | Workflow directory file inventory | P05-CI-01 |
|
||||
| [p05-ci.yml](p05-ci.yml) | Isolated account/login/backend CI verification on Gitea | P05-CI-01/P05-CI-02 |
|
||||
| [p05-backend-acceptance.yml](p05-backend-acceptance.yml) | Manual backend-only disposable Compose, persistence and OIDC acceptance; no Account/Login build rerun | P05-CI-03 |
|
||||
| [p05-security-acceptance.yml](p05-security-acceptance.yml) | Manual isolated Account/Login frozen builds, security advisory triage and strict Moderate+ gate | P05-SEC-01 |
|
||||
@@ -10,6 +10,8 @@ Job responsibilities:
|
||||
|
||||
**P05-CI-02 additions:** Account Portal CI negative route/API smoke, npm/pnpm structured Moderate advisory detail, and disposable Postgres restart persistence plus stronger OIDC issuer/JWKS negative checks. Run #83 passed Account, Login V2 and Security jobs but backend proxy bind to shared host port 8080 failed after Postgres/ZITADEL/Login healthy. **Post-run source fix:** all backend Compose calls include `tests/ci/compose.portless.override.yaml` (`ports: !reset []`), config rejects any published proxy port; this is not CI-verified. Full authenticated user sign-in/MFA remains deferred.
|
||||
|
||||
**P05-SEC-01:** `.gitea/workflows/p05-security-acceptance.yml` is **manual-only** with independent Account frozen build + negative access regressions, Login frozen Nx build + Vitest, Account production audit and Login production audit. Both security jobs require the previous HIGH/CRITICAL gate and a separate STRICT zero Moderate/High/Critical threshold from `tests/ci/security_advisory_gate.py`; any remaining Moderate advisory blocks the security phase. No source authentication changes, deployment or secret use. See `docs/P05-SEC-01.md`.
|
||||
|
||||
**P05-CI-03:** `p05-backend-acceptance.yml` runs **only** the isolated backend job with `tests/ci/backend_acceptance.sh` and always-run `backend_cleanup.sh`. **Gitea Run #86 SUCCESS** on `03fb589`: portless config, all four services, restart persistence, ready/discovery/JWKS, negative cases and complete cleanup passed. No Account/Login build rerun; no production. See `docs/P05-CI-03.md`.
|
||||
|
||||
**Run #81 evidence:** backend's first revision failed during checkout because Alpine had no Git. Added a pre-checkout Git installation afterward; the corrected backend job remains **UNVERIFIED** until a separately approved CI rerun. See `docs/P05-CI-01.md`.
|
||||
|
||||
@@ -0,0 +1,124 @@
|
||||
name: ZitPlane P05-SEC-01 Dependency Security Acceptance
|
||||
|
||||
# Manual only. No PR triggers, production access, real credentials or deployment.
|
||||
on:
|
||||
workflow_dispatch:
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
account:
|
||||
name: Account Portal frozen install, typecheck and production build
|
||||
runs-on: ubuntu-latest
|
||||
container: node:22-bookworm
|
||||
timeout-minutes: 25
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
github-server-url: https://dev.ivib.cc
|
||||
- name: Source/lockfile and auth guard contracts
|
||||
run: |
|
||||
set -eu
|
||||
python3 tests/ci/source_contract.py
|
||||
echo ZITPLANE_SECURITY_SOURCE_LOCK_CONTRACT_PASS
|
||||
- name: Reproducible Account build
|
||||
working-directory: users/ui
|
||||
run: |
|
||||
set -eu
|
||||
npm ci --no-audit --no-fund
|
||||
npm run typecheck
|
||||
npm run build
|
||||
echo ZITPLANE_SECURITY_ACCOUNT_BUILD_PASS
|
||||
- name: Negative Account Portal identity checks (no real user)
|
||||
working-directory: users/ui
|
||||
run: |
|
||||
set -eu
|
||||
export AUTH_SECRET="$(node -e "process.stdout.write(require('node:crypto').randomBytes(48).toString('base64url'))")"
|
||||
export AUTH_URL=https://localhost:3001
|
||||
export AUTH_TRUST_HOST=true
|
||||
export ZITADEL_ISSUER=https://zitadel-ci.invalid
|
||||
export ZITADEL_CLIENT_ID=disposable-negative-only
|
||||
export ZITADEL_CLIENT_SECRET=disposable-negative-only
|
||||
npm run start -- -p 3001 > /tmp/zitplane-security-account.log 2>&1 &
|
||||
server_pid=$!
|
||||
trap 'kill "$server_pid" 2>/dev/null || true' EXIT
|
||||
python3 ../../tests/ci/account_negative.py
|
||||
echo ZITPLANE_SECURITY_ACCOUNT_NEGATIVE_REGRESSIONS_PASS
|
||||
|
||||
login:
|
||||
name: Login V2 pnpm frozen build and unit regressions
|
||||
runs-on: ubuntu-latest
|
||||
container: node:22-bookworm
|
||||
timeout-minutes: 55
|
||||
env:
|
||||
NX_NO_CLOUD: "true"
|
||||
NX_DAEMON: "false"
|
||||
CI: "true"
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
github-server-url: https://dev.ivib.cc
|
||||
- name: Exact pinned pnpm frozen workspace install
|
||||
working-directory: auth/ui/v2
|
||||
run: |
|
||||
set -eu
|
||||
corepack enable
|
||||
corepack prepare pnpm@10.30.3 --activate
|
||||
pnpm install --frozen-lockfile
|
||||
echo ZITPLANE_SECURITY_LOGIN_FROZEN_INSTALL_PASS
|
||||
- name: Build original proto, client and Login V2 with security-only dependencies
|
||||
working-directory: auth/ui/v2
|
||||
run: |
|
||||
set -eu
|
||||
: > apps/login/.env
|
||||
trap 'rm -f apps/login/.env' EXIT
|
||||
pnpm exec nx run @zitadel/login:build --skip-nx-cache
|
||||
test -f apps/login/.next/standalone/apps/login/server.js
|
||||
echo ZITPLANE_SECURITY_LOGIN_BUILD_PASS
|
||||
- name: Unmodified upstream Login V2 Vitest regressions
|
||||
working-directory: auth/ui/v2
|
||||
run: |
|
||||
set -eu
|
||||
pnpm --filter @zitadel/login run test-unit
|
||||
echo ZITPLANE_SECURITY_LOGIN_UNIT_PASS
|
||||
|
||||
security_account:
|
||||
name: Account production High/Critical audit and Moderate acceptance
|
||||
runs-on: ubuntu-latest
|
||||
container: node:22-bookworm
|
||||
timeout-minutes: 20
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
github-server-url: https://dev.ivib.cc
|
||||
- name: Fail-closed production advisory audit
|
||||
working-directory: users/ui
|
||||
run: |
|
||||
set -eu
|
||||
npm audit --omit=dev --audit-level=high
|
||||
echo ZITPLANE_SECURITY_ACCOUNT_HIGH_CRITICAL_GATE_PASS
|
||||
npm audit --omit=dev --json > /tmp/zitplane-sec-account.json || true
|
||||
python3 ../../tests/ci/advisory_triage.py npm /tmp/zitplane-sec-account.json
|
||||
python3 ../../tests/ci/security_advisory_gate.py npm /tmp/zitplane-sec-account.json
|
||||
|
||||
security_login:
|
||||
name: Login production High/Critical audit and Moderate acceptance
|
||||
runs-on: ubuntu-latest
|
||||
container: node:22-bookworm
|
||||
timeout-minutes: 25
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
github-server-url: https://dev.ivib.cc
|
||||
- name: Fail-closed pinned pnpm production advisory audit
|
||||
working-directory: auth/ui/v2
|
||||
run: |
|
||||
set -eu
|
||||
corepack enable
|
||||
corepack prepare pnpm@10.30.3 --activate
|
||||
pnpm audit --prod --audit-level high
|
||||
echo ZITPLANE_SECURITY_LOGIN_HIGH_CRITICAL_GATE_PASS
|
||||
pnpm audit --prod --json > /tmp/zitplane-sec-login.json || true
|
||||
python3 ../../../tests/ci/advisory_triage.py pnpm /tmp/zitplane-sec-login.json
|
||||
python3 ../../../tests/ci/security_advisory_gate.py pnpm /tmp/zitplane-sec-login.json
|
||||
@@ -10,6 +10,7 @@ Compact, developer-friendly monorepo for a central identity service, a branded l
|
||||
- **P05-CI-01:** Manual Gitea Run #81 **overall FAILURE**: Login V2 build + 1219 unit tests PASS, high/critical gate PASS (18 Moderate Login findings), Account Auth.js TS2345 and Docker checkout FAIL. Details: `docs/P05-CI-01.md`.
|
||||
- **P05-CI-02:** Gitea Run #83 **3 PASS / 1 FAIL**. Account Portal typecheck/build and negative identity checks PASS; Login V2 build + 1219/1219 tests PASS; High/Critical security threshold PASS (18 Moderate Login records + 1 Moderate Account package OPEN). Docker Postgres/ZITADEL API/Login healthy, but shared runner port 8080 blocked Traefik; cleanup PASS. CI-only portless override added afterward **not CI-verified**; full OIDC E2E deferred. See `docs/P05-CI-02.md`.
|
||||
- **P05-CI-03:** **Gitea Run #86 SUCCESS** on `03fb589`: portless Docker Compose, four healthy/running services, PostgreSQL restart persistence, ZITADEL readiness, OIDC discovery/JWKS, negative contracts and complete CI cleanup verified. No repeated Account/Login suites. Full interactive OIDC E2E and Moderate dependency fixes remain pending. See `docs/P05-CI-03.md`.
|
||||
- **P05-SEC-01:** Security dependency patch candidates prepared: Account/Login Next.js `16.4.6`, coordinated Login OpenTelemetry `0.80.0/0.222.0`; generated npm/pnpm lock metadata without local application installs/builds/tests. Two transitive `glob`/`minimatch` Moderate advisories remain potential blockers pending exact registry CI; dedicated manual workflow has strict zero-Moderate gate. See `docs/P05-SEC-01.md`.
|
||||
- **Production / Coolify:** not configured or deployed.
|
||||
|
||||
## Documentation and project knowledge
|
||||
|
||||
@@ -36,12 +36,12 @@
|
||||
"@headlessui/react": "^2.2.10",
|
||||
"@heroicons/react": "^2.2.0",
|
||||
"@opentelemetry/api": "^1.9.1",
|
||||
"@opentelemetry/api-logs": "^0.218.0",
|
||||
"@opentelemetry/auto-instrumentations-node": "^0.76.0",
|
||||
"@opentelemetry/api-logs": "^0.222.0",
|
||||
"@opentelemetry/auto-instrumentations-node": "^0.80.0",
|
||||
"@opentelemetry/resource-detector-container": "^0.8.8",
|
||||
"@opentelemetry/resource-detector-gcp": "^0.53.0",
|
||||
"@opentelemetry/resources": "^2.7.1",
|
||||
"@opentelemetry/sdk-node": "^0.218.0",
|
||||
"@opentelemetry/sdk-node": "^0.222.0",
|
||||
"@opentelemetry/winston-transport": "^0.28.0",
|
||||
"@radix-ui/react-tooltip": "^1.2.8",
|
||||
"@tailwindcss/forms": "^0.5.11",
|
||||
@@ -51,7 +51,7 @@
|
||||
"lru-cache": "^11.3.6",
|
||||
"lucide-react": "^0.577.0",
|
||||
"moment": "^2.31.0",
|
||||
"next": "16.4.3",
|
||||
"next": "16.4.6",
|
||||
"next-intl": "^4.11.2",
|
||||
"next-themes": "^0.4.6",
|
||||
"nice-grpc": "^2.1.16",
|
||||
@@ -67,7 +67,7 @@
|
||||
"devDependencies": {
|
||||
"@eslint/js": "^10.0.1",
|
||||
"@faker-js/faker": "^10.6.0",
|
||||
"@next/eslint-plugin-next": "16.4.3",
|
||||
"@next/eslint-plugin-next": "16.4.6",
|
||||
"@opentelemetry/sdk-trace-base": "^2.7.1",
|
||||
"@opentelemetry/sdk-trace-node": "^2.7.1",
|
||||
"@otplib/core": "^12.0.1",
|
||||
|
||||
Generated
+668
-9211
File diff suppressed because it is too large.
Load diff
@@ -17,7 +17,8 @@ Snapshot: 2026-11-22, **Gitea P05-CI-03 Run #86 backend-only SUCCESS** on `03fb5
|
||||
| Mutable profile editing / device sessions / identity deletion | No | N/A | No |
|
||||
| Global ZITADEL SSO logout | No | N/A | No |
|
||||
| Subscriptions, payments and SaaS billing | Outside ZitPlane scope | N/A | No |
|
||||
| Gitea Actions CI verification workflow | Yes, P05 manual dispatch | Run #83 full workflow 3 PASS / 1 FAIL; **Run #86 backend-only SUCCESS**, without rerunning other jobs | Not deployed |
|
||||
| Gitea Actions CI verification workflow | Yes, P05 manual dispatch | Run #83 Account/Login/Security baseline, Run #86 backend-only SUCCESS; P05-SEC-01 patched dependency workflow pending | Not deployed |
|
||||
| Dependency Moderate security patch/acceptance | P05-SEC-01 manifest and lockfile candidates; strict independent CI gates | **NOT YET CI VERIFIED**: original 18 Login Moderate records and 1 Account package; glob/minimatch likely unresolved | Not deployed |
|
||||
| Gitea Actions CI and isolated integration tests | Backend-only workflow; interactive identity E2E remains absent | **Run #86 PASS:** disposable backend OIDC ready/discovery/JWKS, Postgres persistence, cleanup; authenticated user E2E pending | No |
|
||||
| Coolify production stack, TLS, routing and backups | No | No | No |
|
||||
| Public `auth.vib.tools/login` URL | Proposed only | No | No |
|
||||
|
||||
@@ -10,6 +10,7 @@ Every file listed below is a direct child of `docs/`. Add/remove rows whenever t
|
||||
| [P05-CI-01.md](P05-CI-01.md) | Gitea Actions manual verification workflow, gates, limitations and real run evidence | P05-CI-01 / Run #81 complete, acceptance blocked |
|
||||
| [P05-CI-02.md](P05-CI-02.md) | TypeScript remediation, Gitea CI verification, dependency risk and isolation evidence | P05-CI-02 / run #83 done; Docker acceptance blocked |
|
||||
| [P05-CI-03.md](P05-CI-03.md) | Isolated backend-only Gitea CI procedure, checks and exact run outcomes | P05-CI-03 / Run #86 SUCCESS |
|
||||
| [P05-SEC-01.md](P05-SEC-01.md) | Source-grounded dependency security patches, advisory blockers and CI verification | P05-SEC-01 / awaiting Gitea CI |
|
||||
| [SETUP-GUIDE.md](SETUP-GUIDE.md) | Operator/developer prerequisites, configs, activation and safety | DOCS-01 / active; runtime pending |
|
||||
| [FEATURES-STATUS.md](FEATURES-STATUS.md) | Exact implemented/unavailable/unverified feature matrix | DOCS-01 / active |
|
||||
| [TROUBLESHOOTING.md](TROUBLESHOOTING.md) | Known blockers and safe diagnosis based on source status | DOCS-01 / active |
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
# P05-SEC-01 — Dependency Security Remediation & Acceptance
|
||||
|
||||
**Date:** 2026-11-22
|
||||
**Approved baseline:** `1a602551ad9a791efcc594834f2fa6ce748339ae`
|
||||
**State:** Source patch prepared; one focused Gitea security CI cycle pending.
|
||||
|
||||
## Scope and goals
|
||||
|
||||
Reduce verified Moderate advisories from the Gitea Run #83 audit without changing login/authentication logic, user interface, ZITADEL Go backend, Docker Compose, production configuration or real data. The original official Login V2 v4.20.4 **source code** remains byte-for-byte unchanged; only its approved `apps/login/package.json` and workspace lockfile dependency declarations/resolutions are patched.
|
||||
|
||||
## Dependency changes
|
||||
|
||||
- **Account Portal:** direct `next` pinned `16.4.3 → 16.4.6`, with npm v3 lockfile metadata generated without local application dependency installation or scripts. React, Auth.js, TypeScript and application code unchanged.
|
||||
- **Official Login V2 workspace:** direct `next` `16.4.3 → 16.4.6`; matching development `@next/eslint-plugin-next` `16.4.3 → 16.4.6`. Existing `@opentelemetry/auto-instrumentations-node` `^0.76.0 → ^0.80.0`, associated `@opentelemetry/sdk-node` `^0.218.0 → ^0.222.0` and `@opentelemetry/api-logs` `^0.218.0 → ^0.222.0` use a compatible SDK/instrumentation release family. PNPM v10.30.3 re-resolved **lockfile metadata only** (no local project node_modules).
|
||||
- **Lockfile maintenance:** pnpm pruned previously retained unreachable snapshot entries from the originally imported full upstream workspace after resolving the four explicitly imported workspace members. This changes many **lock metadata** lines but does not delete source files, modules, auth code or P02 Compose. Gitea frozen install/build is the required acceptance gate.
|
||||
|
||||
## Security advisory disposition before focused CI
|
||||
|
||||
**Prior baseline from Run #83:** 18 Moderate Login records and one Moderate Account vulnerable `next` package record. Detailed IDs, direct parent paths, fixed version ranges and current lock resolutions: `project/DEPENDENCY-SECURITY.md`, with the full original live audit in `notes/P05-CI-02.md`.
|
||||
|
||||
Next.js seven advisories are mitigated **in source dependency declarations** by `next@16.4.6`; nine previously reported OpenTelemetry records use a coordinated patched SDK/instrumentation family. Neither is claimed resolved until **new registry audit and frozen build pass in CI**.
|
||||
|
||||
Two additional Login workspace Moderate advisories are not safely patchable under this scope:
|
||||
- `GHSA-3g3m-2fjr-6pw4`, `glob@10.5.0`, patched at `14.0.2` or later. Root transitive parents such as `@npmcli/package-json`, `rimraf`, `archiver-utils` still require older glob major.
|
||||
- `GHSA-g3hv-75wg-m249`, `minimatch@10.2.x`, patched at `11.0.1` or later. Parents include `eslint`, `@eslint/config-array`, `nx` and other tooling. Root PNPM overrides are in **read-only** `auth/ui/v2/pnpm-workspace.yaml`, so a forced major override would violate Scope Lock and require compatibility testing.
|
||||
|
||||
These must remain OPEN if confirmed in the current CI report; a moderate gate will **fail rather than silently suppress them**. No `pnpm audit --fix`, `npm audit fix --force` or destructive lockfile workaround is permitted.
|
||||
|
||||
## Gitea Actions (manual only)
|
||||
|
||||
Use **Actions → ZitPlane P05-SEC-01 Dependency Security Acceptance → Run workflow on main** after the source commit is pushed. Dedicated workflow `.gitea/workflows/p05-security-acceptance.yml` has four independent CI jobs:
|
||||
|
||||
1. Account `npm ci`, TypeScript check, Next production build and anonymous API/redirect regression.
|
||||
2. Login pinned PNPM frozen install, original Nx proto/client/Login standalone build and upstream Vitest regression suite.
|
||||
3. Account High/Critical audit (fail-closed), machine-readable audit and **zero Moderate/High/Critical** acceptance gate.
|
||||
4. Login High/Critical audit (fail-closed), machine-readable audit and **zero Moderate/High/Critical** acceptance gate.
|
||||
|
||||
Separate build and audit jobs preserve useful evidence even if remaining advisories block security acceptance. CI uses no production secrets/domains and no local PC application test/build.
|
||||
|
||||
## Acceptance and boundaries
|
||||
|
||||
**Security acceptance requires both dependency audits at zero Moderate/High/Critical, frozen installs and application builds/tests PASS**, with exact evidence and no out-of-scope changes. A nonzero Moderate finding is explicitly a **BLOCKED** gate even when build jobs PASS.
|
||||
|
||||
**PENDING REAL CI:** run ID, SHA, individual job results, current vulnerabilities and follow-up needed. Full authenticated OIDC callback, MFA, Admin Console login, global SSO and production deployment are outside this phase. See `notes/P05-SEC-01.md` for pre-change plan/closure log.
|
||||
@@ -53,6 +53,12 @@ Implement one explicitly approved phase at a time. Keep out-of-scope files, exis
|
||||
- One focused isolated run after source commit/push, no local test/build/Docker, no repeated Account/Login suites, no real users/secrets or production deployment. Full interactive login/MFA remains a separate phase.
|
||||
- **Gitea Actions Run #86 SUCCESS** on `03fb58954dec886128a4011b6121754cbcdd79ff`: portless effective config PASS, all four services ready, disposable PostgreSQL marker persisted after restart, ZITADEL ready/OIDC issuer/discovery/JWKS and negative contracts PASS, CI-owned network/containers/volumes cleanup verified PASS. No Account/Login build rerun, no local build/Docker. Full interactive OIDC login/MFA and Moderate dependencies remain outside this phase. Evidence: `notes/P05-CI-03.md`, `docs/P05-CI-03.md`.
|
||||
|
||||
## P05-SEC-01 - Dependency Security Remediation (APPROVED 2026-11-22)
|
||||
- Baseline `1a602551ad9a791efcc594834f2fa6ce748339ae`. Previous Run #83 security: 18 Moderate Login advisory records and 1 Moderate Account vulnerable Next.js package; Run #86 backend-only SUCCESS.
|
||||
- Narrow approved manifest writes: `users/ui/{package.json,package-lock.json}`, `auth/ui/v2/apps/login/package.json`, root `auth/ui/v2/{package.json,pnpm-lock.yaml}` only if justified; new `.gitea/workflows/p05-security-acceptance.yml`, focused `tests/ci/**`, notes/project/docs and associated README/MINIFEST. **`pnpm-workspace.yaml`, application source, Go backend, developer Compose, production and unrelated files remain read-only.**
|
||||
- Direct Next.js pinned 16.4.6; Login coordinated OTel auto-instrumentation 0.80.0 / SDK 0.222.0 family, PNPM/npm metadata-only lockfile reconciliation. Root overrides are read-only, so glob14/minimatch11 major transitive remediation remains an explicit blocker if registry audit reproduces it.
|
||||
- Dedicated manual Gitea CI: independent Account/Login frozen installs and builds/regressions, plus separate fail-closed HIGH+ gates and **zero Moderate/High/Critical** gates. Exactly one run, accurate unresolved audit evidence; no local app build/test/dev server or production deployment. Details: `notes/P05-SEC-01.md`, `docs/P05-SEC-01.md`.
|
||||
|
||||
## P05 - Full Integration (proposed, NOT approved)
|
||||
Shared design system, production-safe Compose topology and verified Login/Account OIDC wiring. No live deployment; separate approval.
|
||||
|
||||
|
||||
+1
-1
@@ -26,4 +26,4 @@
|
||||
Full update policy is in root [AGENTS.md](../AGENTS.md). A list of available docs is in [MINIFEST.md](MINIFEST.md).
|
||||
|
||||
|
||||
For backend-only isolated runtime verification see [P05-CI-03.md](P05-CI-03.md); for initial full workflow and its limitations see [P05-CI-01.md](P05-CI-01.md). A green backend discovery smoke is not an authenticated user-login result.
|
||||
For dependency security patches and remaining audit blockers see [P05-SEC-01.md](P05-SEC-01.md). For backend-only isolated runtime verification see [P05-CI-03.md](P05-CI-03.md); for initial full workflow and its limitations see [P05-CI-01.md](P05-CI-01.md). A green backend discovery smoke is not an authenticated user-login result.
|
||||
@@ -76,3 +76,8 @@ In Gitea `vibtools/ZitPlane` → **Actions** → **ZitPlane P05-CI-03 Backend Ac
|
||||
|
||||
|
||||
**P05-CI-03 verified result:** Gitea [Run #86](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/86) **SUCCESS** on source SHA `03fb589`. It confirmed the portless CI backend configuration, four-service readiness, PostgreSQL marker persistence after restart, ZITADEL OIDC discovery/JWKS and complete CI-owned cleanup. This **does not** mean the developer PC or production Coolify instance is configured, nor does it prove an authenticated user login/MFA. The run did not repeat earlier Account/Login builds. See `docs/P05-CI-03.md` for evidence.
|
||||
|
||||
|
||||
## P05-SEC-01 security acceptance on Gitea (manual only)
|
||||
|
||||
On Gitea `vibtools/ZitPlane` open Actions → `ZitPlane P05-SEC-01 Dependency Security Acceptance` → Run workflow on `main` **after** the approved source commit is pushed. Jobs use fresh CI runner containers, immutable committed npm/pnpm locks, and no production identity credentials. Account/official Login V2 reproducible builds and unit/negative regressions run separately from Account and Login registry audits. Audits fail if there is **any** Moderate, High or Critical finding; the script prints exact advisory IDs so an outstanding transitive dependency can be fixed in another explicit Scope Lock. The P02 developer Compose, local Windows PC and production Coolify are not modified. See `docs/P05-SEC-01.md` and `project/DEPENDENCY-SECURITY.md`.
|
||||
@@ -24,7 +24,7 @@ Include environment (local disposable vs CI vs production), exact phase/commit,
|
||||
|
||||
- Prior Account Portal `TS2345` at `src/auth.ts(14,61)` in Gitea Run #81 was fixed by verified JWT subject narrowing; Gitea Run #83 Account Portal typecheck/build **PASS**.
|
||||
- Previous Alpine backend checkout missed Git; Run #83 verified the fix. Run #83 also exposed an occupied shared-runner host TCP 8080. **Run #86 verified the portless CI Compose overlay**: all four services ready, disposable Postgres restart persistence, ZITADEL ready/OIDC discovery/JWKS and complete CI-only cleanup PASS. This does **not** prove the separate P02 local PC Compose or real user login.
|
||||
- A green HIGH/CRITICAL advisory audit gate still allows Moderate findings; the P05-CI-02 registry detail report records IDs/package/fix separately, without package upgrades.
|
||||
- A green HIGH/CRITICAL advisory audit gate still allows Moderate findings. P05-SEC-01 updates only approved Next.js/OTel dependency manifests and lockfiles and adds an independent **zero Moderate/High/Critical** acceptance gate. Potential `glob`/`minimatch` transitive major-version issues remain open until a real registry CI audit proves otherwise; no suppressions or forced compatibility-breaking overrides.
|
||||
- CI negative access tests do not simulate real login; actual OIDC app registration/authorized login/MFA must receive separate approval.
|
||||
|
||||
## Known limitations
|
||||
|
||||
@@ -12,5 +12,6 @@ This is the chronological **index**. Phase-specific scope/implementation evidenc
|
||||
| 2026-11-22 | P05-CI-01 | Gitea verification workflow, dependency lock reconciliation, narrow checkout remediation | Run #81: 2 PASS/2 FAIL; 1219 Login tests PASS, Account TS2345 and Docker checkout blocked; see [P05-CI-01.md](P05-CI-01.md) |
|
||||
| 2026-11-22 | P05-CI-02 | Narrow Auth.js TS2345 fix, CI negative tests, advisory triage and post-run portless override | Run #83: Account/Login/Security PASS, Docker FAIL on host 8080; cleanup PASS; portless override unverified. [Evidence](P05-CI-02.md) |
|
||||
| 2026-11-22 | P05-CI-03 | Backend-only Gitea verification of portless Compose, 4 services, Postgres persistence, OIDC/JWKS and safe cleanup | **Run #86 SUCCESS** on `03fb589`, no unrelated suites rerun; [evidence](P05-CI-03.md) |
|
||||
| 2026-11-22 | P05-SEC-01 | Narrow Next.js 16.4.6 and compatible OTel instrumentation security versions, frozen lockfiles, strict CI advisory gate | Implementation source staged; one Gitea security acceptance run pending; [details](P05-SEC-01.md) |
|
||||
|
||||
Rules: Append new phases or fixes; never silently rewrite a past result. Separate **implemented**, **verified**, **blocked**, and **proposed**. Never log a user secret or personal data.
|
||||
@@ -8,6 +8,7 @@
|
||||
| [P05-CI-01.md](P05-CI-01.md) | Scope/roots, allowed paths, implementation and Gitea CI acceptance evidence | P05-CI-01 / source complete, CI blockers open |
|
||||
| [P05-CI-02.md](P05-CI-02.md) | Auth.js narrow patch, isolated Gitea CI gate, advisory triage and exact acceptance evidence | P05-CI-02 / run #83 completed; residual Docker gate blocked |
|
||||
| [P05-CI-03.md](P05-CI-03.md) | Backend-only pre-change scope, disposable CI run evidence and exact acceptance result | P05-CI-03 / Run #86 SUCCESS; acceptance complete |
|
||||
| [P05-SEC-01.md](P05-SEC-01.md) | Pre-change security scope, remediation, exact advisory evidence, one CI run and closure | P05-SEC-01 / source prepared, CI pending |
|
||||
| [CHANGELOG.md](CHANGELOG.md) | Short append-only chronological phase log and links to detailed reports | DOCS-01 / active |
|
||||
|
||||
Update this manifest whenever any direct child file or directory changes. Use **actual source state**; a planned file must be labeled planned, not present.
|
||||
@@ -0,0 +1,47 @@
|
||||
# P05-SEC-01 — Dependency Security Remediation
|
||||
|
||||
**Date:** 2026-11-22
|
||||
**Approved baseline:** `1a602551ad9a791efcc594834f2fa6ce748339ae` (Gitea `main`)
|
||||
**Pre-change status:** APPROVED / PLAN LOCKED; source edits not started.
|
||||
**Prior evidence:** Gitea Run [#83](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/83) security job #173; Run [#86](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/86) disposable backend ACCEPTED.
|
||||
|
||||
## Exact Scope Lock
|
||||
|
||||
Write only: `users/ui/package.json`, `users/ui/package-lock.json`, `auth/ui/v2/apps/login/package.json`, `auth/ui/v2/package.json`, `auth/ui/v2/pnpm-lock.yaml` only as justified; new `.gitea/workflows/p05-security-acceptance.yml`, `tests/ci/**`, `notes/**`, `project/**`, relevant `docs/**`, CI README/MINIFEST, root README/MINIFEST only if needed.
|
||||
Read-only: `auth/ui/v2/apps/login/**` other than approved package.json, `auth/ui/v2/pnpm-workspace.yaml`, all `users/ui/src/**`, `core/backend/zitadel/**`, `deployment/docker/**`, upstream Login logic/other packages, secrets, production systems and untracked `AI_INSTRUCTIONS.md`.
|
||||
|
||||
**No local application builds/tests/dev servers or Docker.** Metadata-only package lock regeneration to satisfy explicitly approved lockfile reconciliation is permitted without installing project node_modules, using `--package-lock-only --ignore-scripts` and pnpm `--lockfile-only --ignore-scripts`. One Gitea Actions CI acceptance cycle, not a rerun loop.
|
||||
|
||||
## Exact prior advisory evidence
|
||||
|
||||
**Account:** npm audit reports one `next` package affected by 7 GHSA advisories:
|
||||
`GHSA-mfr8-8qww-v76h`,
|
||||
`GHSA-vc7v-qv4w-wrv8`,
|
||||
`GHSA-7qx7-33qx-rqx2`,
|
||||
`GHSA-f3mh-rxg3-f5g2`,
|
||||
`GHSA-pc58-hwjq-p385`,
|
||||
`GHSA-rhh4-g77r-r9qj`,
|
||||
`GHSA-vvgp-ww4w-46vf`.
|
||||
Root source pins `next@16.4.3`; npm registry advisory shows vulnerable 16.0.0–16.4.4 and patch `16.4.6` (same minor release).
|
||||
|
||||
**Login workspace:** 18 Moderate **advisory records** (not 18 distinct CVEs or necessarily 18 exposed runtime code paths):
|
||||
- 8 vulnerable instrumentations under `GHSA-qqmp-wf37-98f9` (DB username recorded in telemetry spans): `@opentelemetry/instrumentation-{pg,mysql2,knex,mysql,mongoose,oracledb,tedious,cassandra-driver}`. Parent `@opentelemetry/auto-instrumentations-node@0.76.0` direct login dependency; root production instrumentation flow must not be modified. Minimum fixes respectively pg 0.73.0; mysql2 0.67.0; knex 0.65.0; mysql 0.67.0; mongoose 0.67.0; oracledb 0.46.0; tedious 0.40.0; cassandra-driver 0.66.0.
|
||||
- `GHSA-3v2p-hm54-8qcq`: `@opentelemetry/instrumentation-http`, fixed >=0.222.0.
|
||||
- `GHSA-3g3m-2fjr-6pw4`: `glob`, fixed >=14.0.2; risk of continued filesystem traversal after cancellation.
|
||||
- `GHSA-g3hv-75wg-m249`: `minimatch`, fixed >=11.0.1; globparts pattern amplification DoS.
|
||||
- Same 7 Next.js GHSAs as Account for `next@16.4.3`; registry suggests patched >=16.4.5, account audit recommends 16.4.6.
|
||||
|
||||
**Prior High/Critical:** 0 in both production audits on Run #83; moderate issues remain OPEN until security CI actually passes.
|
||||
|
||||
## Pre-change investigation and implementation plan
|
||||
|
||||
1. Inspect current exact importer, pnpm override settings (existing `pnpm-workspace.yaml` READ ONLY), lockfile package versions and dependency parent paths. Compare npm registry metadata and official advisory fixed ranges. Classify direct vs transitive, production reachability and compatibility.
|
||||
2. Apply justified exact `next@16.4.6` pins in Account and Login app plus aligned `@next/eslint-plugin-next` only if necessary within approved login package.json. Reconcile Account npm lock metadata-only, no package installation or scripts.
|
||||
3. For 8 OTel packages, OTel HTTP, glob and minimatch, prefer compatible parent release/resolution that satisfies fixed advisory ranges without source change. pnpm override configuration is outside approved `pnpm-workspace.yaml`; if compatible parent/version/lock changes cannot be proven within current write scope, **document precise blockers and defer**, rather than edit excluded file, fabricate resolved status or use broad incompatible overrides.
|
||||
4. Regenerate narrowly justified pnpm lock metadata using pinned pnpm; verify frozen importer specs, tracked scope, exact patch/security audit, no secrets and original Login V2 auth source unchanged.
|
||||
5. Add **manual-only** isolated Gitea security acceptance workflow with frozen npm/pnpm installs, fail-closed HIGH/CRITICAL and separate Moderate advisory inventory/gate (any Moderate remaining => FAIL/explicit blocker), Account typecheck/production build and Login V2 Nx proto/client/standalone build plus focused relevant unit suite.
|
||||
6. Source audit, docs/manifests sync, one scoped commit/push to Gitea main and exact remote SHA verification; **one CI cycle**. Record real run IDs/results and unresolved vulnerabilities, no false PASS. End with documentation/result commit/push and next exact phase lock/approval.
|
||||
|
||||
## Phase evidence ledger
|
||||
|
||||
**PENDING.** Update with actual modifications and one focused CI run SHA/job conclusions. If Moderate remain, security closure must stay **BLOCKED**, not silently accepted.
|
||||
@@ -12,6 +12,7 @@ This is the **developer-focused implementation history**. `notes/CHANGELOG.md` i
|
||||
| 2026-11-22 | P05-CI-01 | `.gitea/workflows/p05-ci.yml`, `tests/ci/**`, Account npm lock, Login pnpm importer reconciliation and in-scope Alpine Git checkout correction | Run #81 overall FAIL; 2 jobs PASS, 2 FAIL; Login 1219/1219 tests PASS, Account TS2345 and Docker checkout blocked; `notes/P05-CI-01.md` |
|
||||
| 2026-11-22 | P05-CI-02 | Type-safe Auth.js subject narrowing, Account anonymous negative tests, Login regression, structured advisory triage and CI-only portless Docker override | Run #83: 3 PASS/1 FAIL; Docker proxy 8080 collision, cleanup PASS, portless fix unverified; see `notes/P05-CI-02.md` |
|
||||
| 2026-11-22 | P05-CI-03 | Dedicated manual backend-only CI acceptance, guarded disposable Compose, persistence/ready/JWKS probes and owned-state cleanup | **Gitea Run #86 SUCCESS** on `03fb589`; all steps PASS; `notes/P05-CI-03.md` |
|
||||
| 2026-11-22 | P05-SEC-01 | Next.js/OTel minimal security manifest and metadata-only locks; strict Moderate+ audits and build/regression CI; no app/UI source modifications | Source under review, one Gitea CI cycle pending; `notes/P05-SEC-01.md` |
|
||||
|
||||
## Required entry for each future change
|
||||
|
||||
|
||||
@@ -82,3 +82,12 @@ This phase can verify local disposable backend runtime only. It **cannot** certi
|
||||
Gitea manual backend-only [Run #86](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/86), job #184, tested `03fb58954dec886128a4011b6121754cbcdd79ff`; **SUCCESS**. The Git checkout, isolated acceptance and always-run cleanup steps all succeeded. P02 3/3 backend contract tests, combined portless config, four service health, disposable Postgres write/restart/read marker, local ZITADEL readiness, exact issuer metadata, OIDC discovery, nonempty JWKS and malformed-input contract checks each produced real PASS markers. The CI-owned network, containers and named volumes were removed; no host TCP 8080 binding remained. Docker v29.9.3 and Compose v5.7.2 used on the runner.
|
||||
|
||||
This confirms **disposable backend acceptance**, not ZITADEL Console user login, Account Portal positive/authenticated callback, real MFA, global SSO, production routing or Moderate advisory remediation. The original P02 Compose and official source/lock versions remain untouched. No repeated Account/Login build/test jobs ran in P05-CI-03. Runtime outcome recorded in `notes/P05-CI-03.md` and `docs/P05-CI-03.md`; final docs-only commit is not a new tested binary/SHA.
|
||||
|
||||
|
||||
## P05-SEC-01 — Independent frozen-build and strict dependency audit gates
|
||||
|
||||
Manual Gitea-only `.gitea/workflows/p05-security-acceptance.yml` has four independent jobs: Account `npm ci`/TypeScript/Next.js build plus anonymous negative route checks; official Login V2 `pnpm@10.30.3 install --frozen-lockfile`, Nx proto/client/standalone build and upstream Vitest regression; standalone Account production registry audit; standalone Login workspace production registry audit. Independent jobs prevent a remaining Moderate advisory from hiding build/test results.
|
||||
|
||||
Each registry job first runs `npm audit --omit=dev --audit-level=high` or `pnpm audit --prod --audit-level high` under `set -eu` to fail-closed on High/Critical. Then nonmutating JSON is collected, `tests/ci/advisory_triage.py` prints exact IDs/package/range/fix, and `tests/ci/security_advisory_gate.py` requires complete/count-consistent JSON and **zero Moderate/High/Critical**. Any Moderate is an actual failed gate, not a warning disguised as acceptance.
|
||||
|
||||
Only approved manifest and lockfile metadata were patched; original Login/auth/API/UI source, `pnpm-workspace.yaml`, P02 backend, Compose, real credentials and production unchanged. Two transitive glob/minimatch risks may remain because the root PNPM override configuration is outside Scope Lock and those require semver-major upgrades. See `project/DEPENDENCY-SECURITY.md` for the original 18+1 records and exact immediate parents; source state is not proof of advisory resolution until actual Gitea run.
|
||||
@@ -0,0 +1,41 @@
|
||||
# ZitPlane P05-SEC-01 — Dependency Provenance, Vulnerabilities and Exact Patch Records
|
||||
|
||||
**Baseline:** `1a602551ad9a791efcc594834f2fa6ce748339ae`
|
||||
**Reference:** Gitea Run #83 security job #173, 2026-11-22. The source-only regenerated npm/pnpm lockfiles are **not CI acceptance** until the subsequent focused security workflow verifies frozen installs and registry advisory results.
|
||||
|
||||
## Advisory inventory (19 prior reported records)
|
||||
|
||||
`npm audit` reported **one affected Account Next.js package** associated with **seven IDs**, not seven different installed npm packages. `pnpm audit --prod` reported **18 Login Moderate records**, representing 7 Next.js IDs, 8 OpenTelemetry driver instrumentation records under a *single GHSA*, 1 HTTP instrumentation advisory, 1 glob and 1 minimatch. Previous HIGH/CRITICAL counts were zero.
|
||||
|
||||
| ID / Group | Affected package(s) and old pin | Verified immediate dependency parent | Security impact / required patched range | Source resolution, pending CI |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Seven Next.js GHSAs below | Account + Login direct `next@16.4.3` | Each application `package.json` | Information/cross-user cache disclosure/poisoning, SVG bypass, Edge HttpOnly header exposure and cross-client response injection; npm fix `16.4.6` | Both apps pin `next@16.4.6` in approved manifest/lock |
|
||||
| `GHSA-qqmp-wf37-98f9` (8 records) | `@opentelemetry/instrumentation-{pg,mysql2,knex,mysql,mongoose,oracledb,tedious,cassandra-driver}` | `@opentelemetry/auto-instrumentations-node@0.76.0` direct production Login dependency | Database account username exposed as `db.user` in spans. Fixed: pg >=0.73.0; mysql2/mysql/mongoose >=0.67.0; knex >=0.65.0; oracledb >=0.46.0; tedious >=0.40.0; cassandra >=0.66.0 | Coordinated parent `auto-instrumentations-node@0.80.0` + `sdk-node@0.222.0` selects patched minors |
|
||||
| `GHSA-3v2p-hm54-8qcq` | `@opentelemetry/instrumentation-http@0.218.0` | `@opentelemetry/auto-instrumentations-node@0.76.0` | Moderate HTTP instrumentation issue, patched >=0.222.0 | `auto-instrumentations-node@0.80.0` requires `instrumentation-http@^0.222.0` |
|
||||
| `GHSA-3g3m-2fjr-6pw4` | `glob@10.5.0`; old lock also `13.0.6` | Snapshot immediate parents: `@npmcli/map-workspaces@3`, `@npmcli/package-json@5`, `rimraf@5`, `archiver-utils@5`, `unified-engine@11`; old `cacache@20` also referenced glob13 | Aborted glob traversal may continue performing costly filesystem operations, risking availability; patched >=14.0.2 | **OPEN**: major 14 not permitted by parent semver/approved root overrides; current workspace YAML read-only |
|
||||
| `GHSA-g3hv-75wg-m249` | `minimatch@10.2.5/10.2.6`; old lock also v9 | Snapshot immediate parents include `eslint@10.8.1`, `@eslint/config-array@0.23.5`, `@typescript-eslint/typescript-estree@8.67.0`, `nx@22.7.12`, `@netlify/build-info@10.5.1` and `glob@13.0.6` | Potential globparts amplification denial of service, patched >=11.0.1 | **OPEN**: major 11 needs compatible transitive parent update or audited PNPM workspace override, outside exact write scope |
|
||||
|
||||
### Seven GitHub advisory IDs affecting Next.js 16.4.3
|
||||
|
||||
`GHSA-mfr8-8qww-v76h`, `GHSA-vc7v-qv4w-wrv8`, `GHSA-7qx7-33qx-rqx2`, `GHSA-f3mh-rxg3-f5g2`, `GHSA-pc58-hwjq-p385`, `GHSA-rhh4-g77r-r9qj`, `GHSA-vvgp-ww4w-46vf`.
|
||||
|
||||
Original audit: Login Next fixed >=16.4.5; Account npm recommends >=16.4.6, so **16.4.6 exact** chosen for both plus matching `@next/eslint-plugin-next` (Login dev only). See https://www.npmjs.com/package/next and original Gitea security logs.
|
||||
|
||||
### Transitive parent and compatibility detail
|
||||
|
||||
This table identifies **immediate parents present in the archived PNPM lock graph**, not a claim that every vulnerable package is loaded at runtime or exploitable over a public request. Actual production reachability remains UNVERIFIED without a separate controlled analysis. PNPM's `--prod` audit flagged these lockfile packages, so they must not be suppressed solely because many parents are dev tools.
|
||||
|
||||
`auth/ui/v2/pnpm-workspace.yaml` already owns other root overrides and is explicitly READ ONLY in this phase. A `pnpm.overrides` entry in root `package.json` would conflict with or be ignored in the presence of workspace-defined overrides on modern PNPM; **no ineffective fake override is added**. Minimatch 11/glob 14 are semver major changes; forcing them without compatibility proof is disallowed.
|
||||
|
||||
### Reproducible lockfile / provenance rules
|
||||
|
||||
- Account npm v3 lock was generated by `npm install --package-lock-only --ignore-scripts --no-audit --no-fund`; **no app install/build/test**.
|
||||
- Login pinned `pnpm@10.30.3` lock was generated by `pnpm install --lockfile-only --ignore-scripts --no-frozen-lockfile`; no project `node_modules`. The four imported PNPM workspace members and prior root overrides are unchanged.
|
||||
- PNPM's lockfile-only regeneration removed prior unreachable snapshots inherited from a much larger official ZITADEL monorepo. Source files/proto/Login UI/auth code are unchanged. Compare exact Git diff: this is **lock resolution metadata**, not removal of application features.
|
||||
- Security acceptance is only the single Gitea workflow run: frozen npm/pnpm installs, locked build/regression and live npm/pnpm advisory results. No blind blanket update, no lockfile hand-edited integrities.
|
||||
|
||||
## Source-level candidate and acceptance
|
||||
|
||||
Expected patched direct candidates: Next.js `16.4.6` both apps; Login `@opentelemetry/auto-instrumentations-node@0.80.0`, `@opentelemetry/sdk-node@0.222.0`, `@opentelemetry/api-logs@0.222.0`. **OPEN candidate blockers:** glob >=14.0.2, minimatch >=11.0.1 require separately approved scoped parent/override changes.
|
||||
|
||||
**CI PENDING:** live audit may expose new or unchanged vulnerabilities; never declare zero Moderate from manifest text alone. The follow-up result record will list all remaining exact IDs, job statuses and a separate narrow remediation plan.
|
||||
@@ -135,3 +135,18 @@ For any approved update:
|
||||
| `docs/P05-CI-03.md`, `notes/P05-CI-03.md` | Public-facing CI procedure and accurate implementation/run evidence |
|
||||
|
||||
P02 dev Compose, core backend helper, Login V2 source, Account Portal and all dependency manifests remain unmodified.
|
||||
|
||||
|
||||
## P05-SEC-01 — Dependency security file ownership
|
||||
|
||||
| Path | Exact authorized behavior |
|
||||
| --- | --- |
|
||||
| `users/ui/package.json` and `users/ui/package-lock.json` | Account Portal direct Next.js 16.4.6 security pin and npm v3 metadata-only lock |
|
||||
| `auth/ui/v2/apps/login/package.json` | Official Login V2 dependency **declaration only**: Next.js/ESLint plugin and coordinated OpenTelemetry SDK/auto instrumentation; original app/auth source untouched |
|
||||
| `auth/ui/v2/pnpm-lock.yaml` | Reproducible PNPM v10.30.3 resolution with pruned unreachable snapshots from former large upstream workspace |
|
||||
| `.gitea/workflows/p05-security-acceptance.yml` | Manual four-job CI: independent Account/Login frozen builds and Account/Login production advisory gates |
|
||||
| `tests/ci/security_advisory_gate.py` | Rejects malformed npm/pnpm JSON or any Moderate/High/Critical audit record; never suppresses or changes packages |
|
||||
| `project/DEPENDENCY-SECURITY.md` | Detailed GHSA/group/parent/versions/patch/risk and CI disposition |
|
||||
| `notes/P05-SEC-01.md`, `docs/P05-SEC-01.md` | Pre-change plan, source patch provenance, actual run results and operator guidance |
|
||||
|
||||
**Read-only:** `auth/ui/v2/pnpm-workspace.yaml`, all `users/ui/src/**`, original Login V2 components/logic, backend/Compose and unrelated monorepo packages.
|
||||
@@ -102,3 +102,10 @@ Workflow service orchestration is in `.gitea/workflows/p05-ci.yml`, not Python.
|
||||
| `backend_cleanup.sh` main | Same | Always-step removes only marked CI project with volumes; verifies no fixed network, matching project containers or volumes persist; no marker => no project teardown |
|
||||
|
||||
The scripts execute in the **Gitea Actions** runner, not on the local developer PC. Real user authentication and MFA are not implemented as CI checks.
|
||||
|
||||
|
||||
## P05-SEC-01 — Security-only CI helper behavior
|
||||
|
||||
`tests/ci/security_advisory_gate.py` owns `main()`: it reads one npm or pnpm production registry audit JSON report, checks for report errors, validates required numeric severity counters and matching npm vulnerable-package or pnpm advisory records, prints the actual counts and **returns a failing CI exit code** if Moderate, High or Critical count is nonzero. Invalid or missing report information is also an error. It does **not** modify package manifests, bypass audit rules or accept a waived advisory. The upstream helper `tests/ci/advisory_triage.py` still displays exact GHSA/package/fix records and remains unchanged.
|
||||
|
||||
Workflow shell commands are written directly under `.gitea/workflows/p05-security-acceptance.yml`. No application runtime function or auth code changed in this phase.
|
||||
@@ -6,6 +6,7 @@
|
||||
| [MINIFEST.md](MINIFEST.md) | Exact direct-child file inventory | DOCS-01 / active |
|
||||
| [ARCHITECTURE.md](ARCHITECTURE.md) | Verified component boundaries, identity flows, future integration boundary | DOCS-01 / active |
|
||||
| [CI-ARCHITECTURE.md](CI-ARCHITECTURE.md) | Gitea runner jobs, dependency reconciliation, disposable infrastructure and remaining auth gates | P05-CI-01 / prepared |
|
||||
| [DEPENDENCY-SECURITY.md](DEPENDENCY-SECURITY.md) | Exact GHSA inventory, transitive parents, minimal patch ranges and CI evidence | P05-SEC-01 / active |
|
||||
| [FILE-MAP.md](FILE-MAP.md) | First-party file + module explanation; upstream source references | DOCS-01 / active |
|
||||
| [FUNCTIONS.md](FUNCTIONS.md) | First-party function/route map, safeguards and responsibilities | DOCS-01 / active |
|
||||
| [FEATURES-AND-PAGES.md](FEATURES-AND-PAGES.md) | Every ZitPlane-owned Account Portal page/API and backend/login capability status | DOCS-01 / active |
|
||||
|
||||
@@ -54,3 +54,12 @@ The runner's published TCP 8080 was already in use, so P02's local-only Traefik
|
||||
## P05-CI-03 backend acceptance — proven in Gitea only
|
||||
|
||||
Run #86 on commit `03fb589` executed a backend-only manual Gitea Actions job and verified the original pinned P02 container images on a disposable Docker v29.9.3 / Compose v5.7.2 runner. The P05 portless CI override removed the developer-only host binding, all four containers came up, PostgreSQL retained a synthetic row across a restart, and ZITADEL ready/issuer/OIDC discovery/JWKS passed. Owned network/containers/volumes were verified removed by the always-run cleanup step. No local PC/docker startup, release or production deployment occurred. Remaining steps before deployment: review/patch 18 Moderate Login findings and 1 Moderate Account `next` package, then disposable authenticated OIDC and Admin Console/MFA tests plus production TLS/Coolify/backup readiness.
|
||||
|
||||
|
||||
## P05-SEC-01 — Frozen dependency security resolution
|
||||
|
||||
- Account: direct `next@16.4.6` and npm v3 lock metadata created with `npm install --package-lock-only --ignore-scripts --no-audit --no-fund`; no local application install/build/test.
|
||||
- Imported Login V2: direct `next@16.4.6`, `@next/eslint-plugin-next@16.4.6`; `@opentelemetry/auto-instrumentations-node@^0.80.0`, `@opentelemetry/sdk-node@^0.222.0`, `@opentelemetry/api-logs@^0.222.0` to align the telemetry release family. PNPM v10.30.3 ran metadata-only `install --lockfile-only --ignore-scripts --no-frozen-lockfile`; no project `node_modules` was created.
|
||||
- The imported PNPM lock previously retained snapshots from an upstream monorepo larger than the 4-member ZitPlane workspace. Regeneration pruned many no-longer-reachable snapshots, with only metadata file changes inside approved scope; root workspace `pnpm-workspace.yaml` and imported code unchanged. The Gitea **frozen install** is the required proof of consistency.
|
||||
- Advisory resolution cannot be claimed merely from versions. `glob@10.5.0` and `minimatch@10.2.x` remain in the lockfile through tooling parents with older major ranges, and the workspace override file is read-only. Their Moderate advisories stay OPEN until proven fixed or separately approved.
|
||||
- Dedicated manual Gitea `p05-security-acceptance.yml` performs Account/Login frozen builds and a strict High/Critical + Moderate gate. Prior P05 backend Run #86 was successful and was **not** deployed.
|
||||
+25
-20
@@ -1,25 +1,25 @@
|
||||
# Source inventory ? all Git-tracked paths
|
||||
|
||||
**Snapshot:** 2026-11-22, P05-CI-03 source and docs based on `4857558`. Dedicated backend-only source commit `03fb589` was **verified PASS** by Gitea Run #86; the subsequent documentation commit is not a new runtime test.
|
||||
**Snapshot:** 2026-11-22, P05-SEC-01 security source on approved baseline `1a60255`; the new security CI run has not yet been executed.
|
||||
|
||||
**Git-tracked files: 724.** Untracked `AI_INSTRUCTIONS.md` and ignored secrets excluded.
|
||||
**Exact Git-tracked paths: 729.** Original upstream source semantics unchanged; untracked `AI_INSTRUCTIONS.md` and ignored local secrets excluded.
|
||||
|
||||
This exact path inventory does not assert every upstream function was inspected. Consult `project/FILE-MAP.md` for first-party roles and `docs/P05-CI-03.md` for acceptance.
|
||||
This is a source locator, not proof of security acceptance. See `project/DEPENDENCY-SECURITY.md` for patch/advisory provenance and `notes/P05-SEC-01.md` for actual CI outcome.
|
||||
|
||||
| Group | Files | Owner/purpose |
|
||||
| Top-level group | Files | Ownership |
|
||||
| --- | ---: | --- |
|
||||
| `(repository root)` | 6 | Root files |
|
||||
| `.gitea` | 6 | Gitea manual CI workflow files |
|
||||
| `auth` | 639 | Official pinned Login V2 source |
|
||||
| `core` | 2 | P02 dev orchestration |
|
||||
| `deployment` | 2 | P02 local Compose |
|
||||
| `docs` | 15 | User/operator guides and phase evidence |
|
||||
| `notes` | 7 | Pre-change plans and phase reports |
|
||||
| `packages` | 1 | First-party package placeholder |
|
||||
| `project` | 10 | Developer file/function/CI mapping |
|
||||
| `(repository root)` | 6 | Git-tracked root |
|
||||
| `.gitea` | 7 | Manual Gitea CI workflows |
|
||||
| `auth` | 639 | Original official Login V2 source plus security-only dependency metadata |
|
||||
| `core` | 2 | Backend dev orchestration |
|
||||
| `deployment` | 2 | Dev-only Compose |
|
||||
| `docs` | 16 | User/operator guides |
|
||||
| `notes` | 8 | Pre-change plans/evidence |
|
||||
| `packages` | 1 | Shared package placeholder |
|
||||
| `project` | 11 | Developer file/functions/security maps |
|
||||
| `scripts` | 1 | Script placeholder |
|
||||
| `tests` | 11 | CI/backend focused contracts |
|
||||
| `users` | 24 | First-party Account Portal |
|
||||
| `tests` | 12 | Focused CI contracts/verification tools |
|
||||
| `users` | 24 | Account Portal/approved manifest and lock |
|
||||
|
||||
## Exact Git-tracked paths
|
||||
|
||||
@@ -32,7 +32,7 @@ This exact path inventory does not assert every upstream function was inspected.
|
||||
- `MINIFEST.md`
|
||||
- `README.md`
|
||||
|
||||
### .gitea ? 6 files
|
||||
### .gitea ? 7 files
|
||||
|
||||
- `.gitea/MINIFEST.md`
|
||||
- `.gitea/README.md`
|
||||
@@ -40,6 +40,7 @@ This exact path inventory does not assert every upstream function was inspected.
|
||||
- `.gitea/workflows/README.md`
|
||||
- `.gitea/workflows/p05-backend-acceptance.yml`
|
||||
- `.gitea/workflows/p05-ci.yml`
|
||||
- `.gitea/workflows/p05-security-acceptance.yml`
|
||||
|
||||
### auth ? 639 files
|
||||
|
||||
@@ -693,7 +694,7 @@ This exact path inventory does not assert every upstream function was inspected.
|
||||
- `deployment/README.md`
|
||||
- `deployment/docker/compose.backend.dev.yaml`
|
||||
|
||||
### docs ? 15 files
|
||||
### docs ? 16 files
|
||||
|
||||
- `docs/ARCHITECTURE.md`
|
||||
- `docs/DEVELOPMENT.md`
|
||||
@@ -705,13 +706,14 @@ This exact path inventory does not assert every upstream function was inspected.
|
||||
- `docs/P05-CI-01.md`
|
||||
- `docs/P05-CI-02.md`
|
||||
- `docs/P05-CI-03.md`
|
||||
- `docs/P05-SEC-01.md`
|
||||
- `docs/PHASES.md`
|
||||
- `docs/README.md`
|
||||
- `docs/SETUP-GUIDE.md`
|
||||
- `docs/TROUBLESHOOTING.md`
|
||||
- `docs/USER-GUIDE.md`
|
||||
|
||||
### notes ? 7 files
|
||||
### notes ? 8 files
|
||||
|
||||
- `notes/CHANGELOG.md`
|
||||
- `notes/DOCS-01.md`
|
||||
@@ -719,17 +721,19 @@ This exact path inventory does not assert every upstream function was inspected.
|
||||
- `notes/P05-CI-01.md`
|
||||
- `notes/P05-CI-02.md`
|
||||
- `notes/P05-CI-03.md`
|
||||
- `notes/P05-SEC-01.md`
|
||||
- `notes/README.md`
|
||||
|
||||
### packages ? 1 files
|
||||
|
||||
- `packages/README.md`
|
||||
|
||||
### project ? 10 files
|
||||
### project ? 11 files
|
||||
|
||||
- `project/ARCHITECTURE.md`
|
||||
- `project/CHANGELOG.md`
|
||||
- `project/CI-ARCHITECTURE.md`
|
||||
- `project/DEPENDENCY-SECURITY.md`
|
||||
- `project/FEATURES-AND-PAGES.md`
|
||||
- `project/FILE-MAP.md`
|
||||
- `project/FUNCTIONS.md`
|
||||
@@ -742,7 +746,7 @@ This exact path inventory does not assert every upstream function was inspected.
|
||||
|
||||
- `scripts/README.md`
|
||||
|
||||
### tests ? 11 files
|
||||
### tests ? 12 files
|
||||
|
||||
- `tests/README.md`
|
||||
- `tests/ci/MINIFEST.md`
|
||||
@@ -753,6 +757,7 @@ This exact path inventory does not assert every upstream function was inspected.
|
||||
- `tests/ci/backend_cleanup.sh`
|
||||
- `tests/ci/compose.portless.override.yaml`
|
||||
- `tests/ci/oidc_discovery.py`
|
||||
- `tests/ci/security_advisory_gate.py`
|
||||
- `tests/ci/source_contract.py`
|
||||
- `tests/test_backend_dev.py`
|
||||
|
||||
|
||||
@@ -11,3 +11,4 @@
|
||||
| [compose.portless.override.yaml](compose.portless.override.yaml) | CI-only override to clear inherited P02 proxy host port publishing; pending CI acceptance | P05-CI-02/P05-CI-03 |
|
||||
| [backend_acceptance.sh](backend_acceptance.sh) | Backend-only runner preflight, four-service health, Postgres restart marker and OIDC/JWKS CI checks | P05-CI-03 |
|
||||
| [backend_cleanup.sh](backend_cleanup.sh) | Always-run cleanup of marked CI-owned Compose project/volumes, with leftover verification | P05-CI-03 |
|
||||
| [security_advisory_gate.py](security_advisory_gate.py) | Strict CI registry JSON gate: rejects incomplete reports and any Moderate/High/Critical finding | P05-SEC-01 |
|
||||
@@ -14,4 +14,6 @@ No real credentials or production domains are used. Never print bootstrap PATs,
|
||||
- `backend_cleanup.sh` (P05-CI-03) is the workflow's `always()` cleanup script. It tears down only a marked run-owned Compose project and verifies that no project containers, volumes or fixed network remain. Unverified cleanup is an explicit failure.
|
||||
- Run from `.gitea/workflows/p05-backend-acceptance.yml` **only in isolated Gitea CI**, not on a production Docker host or local developer PC. **Run #86 PASS** on `03fb589`, including persistence and owned cleanup. No real user login/MFA E2E was run.
|
||||
|
||||
- `security_advisory_gate.py` (P05-SEC-01) takes npm or pnpm registry audit JSON, rejects missing/errored/inconsistent metadata and requires **zero Moderate/High/Critical findings**. It is independent of the existing HIGH+ audit command and `advisory_triage.py` detailed advisory ID report. Do not mark reported Moderate findings resolved without a green CI result. Dedicated `.gitea/workflows/p05-security-acceptance.yml` is manual only; frozen installs/builds run only on Gitea.
|
||||
|
||||
Add new CI checks and update `MINIFEST.md`, `project/`, `docs/`, and `notes/` in the same approved phase.
|
||||
@@ -0,0 +1,76 @@
|
||||
"""Fail-closed production advisory gate: reject Moderate, High and Critical.
|
||||
|
||||
Registry report must be complete and match the expected format.
|
||||
This is CI-only; report data comes from npm/pnpm and never changes dependencies.
|
||||
"""
|
||||
from __future__ import annotations
|
||||
|
||||
import json
|
||||
from pathlib import Path
|
||||
import sys
|
||||
|
||||
LEVELS = ("moderate", "high", "critical")
|
||||
ALL = ("info", "low", "moderate", "high", "critical")
|
||||
|
||||
|
||||
def main() -> int:
|
||||
if len(sys.argv) != 3 or sys.argv[1] not in ("npm", "pnpm"):
|
||||
raise ValueError("Usage: security_advisory_gate.py npm|pnpm report.json")
|
||||
manager, file = sys.argv[1:]
|
||||
report = json.loads(Path(file).read_text(encoding="utf-8"))
|
||||
if not isinstance(report, dict) or report.get("error"):
|
||||
raise ValueError("Registry error or malformed audit report")
|
||||
metadata = report.get("metadata")
|
||||
if not isinstance(metadata, dict):
|
||||
raise ValueError("Audit metadata missing")
|
||||
counts = metadata.get("vulnerabilities")
|
||||
if not isinstance(counts, dict):
|
||||
raise ValueError("Audit vulnerability metadata missing")
|
||||
for severity in ALL:
|
||||
value = counts.get(severity)
|
||||
if type(value) is not int or value < 0:
|
||||
raise ValueError(f"Missing/non-integer {severity} audit count")
|
||||
|
||||
if manager == "npm":
|
||||
packages = report.get("vulnerabilities")
|
||||
if not isinstance(packages, dict):
|
||||
raise ValueError("npm audit vulnerable package map missing")
|
||||
discovered = {severity: 0 for severity in ALL}
|
||||
for name, record in packages.items():
|
||||
if not isinstance(record, dict) or record.get("severity") not in ALL:
|
||||
raise ValueError(f"Invalid npm package vulnerability record: {name}")
|
||||
discovered[record["severity"]] += 1
|
||||
if any(counts[key] != discovered[key] for key in ALL):
|
||||
raise ValueError("npm metadata and individual vulnerable package counts differ")
|
||||
else:
|
||||
records = report.get("advisories")
|
||||
if not isinstance(records, dict):
|
||||
raise ValueError("pnpm audit advisory map missing")
|
||||
discovered = {severity: 0 for severity in ALL}
|
||||
for identifier, record in records.items():
|
||||
if not isinstance(record, dict) or record.get("severity") not in ALL:
|
||||
raise ValueError(f"Invalid pnpm advisory record: {identifier}")
|
||||
discovered[record["severity"]] += 1
|
||||
if any(counts[key] != discovered[key] for key in ALL):
|
||||
raise ValueError("pnpm metadata and individual advisory counts differ")
|
||||
|
||||
print(f"ZITPLANE_{manager.upper()}_ADVISORY_COUNTS={counts}", flush=True)
|
||||
open_count = sum(counts[key] for key in LEVELS)
|
||||
if open_count:
|
||||
print(
|
||||
f"ZITPLANE_{manager.upper()}_SECURITY_ACCEPTANCE_BLOCKED="
|
||||
f"{open_count} Moderate/High/Critical findings; see preceding triage records",
|
||||
file=sys.stderr,
|
||||
flush=True,
|
||||
)
|
||||
return 1
|
||||
print(f"ZITPLANE_{manager.upper()}_ZERO_MODERATE_HIGH_CRITICAL_PASS")
|
||||
return 0
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
try:
|
||||
sys.exit(main())
|
||||
except (ValueError, OSError, KeyError, json.JSONDecodeError) as exc:
|
||||
print(f"ZITPLANE_ADVISORY_GATE_INVALID_REPORT: {exc}", file=sys.stderr)
|
||||
sys.exit(1)
|
||||
Generated
+40
-40
@@ -8,7 +8,7 @@
|
||||
"name": "@zitplane/account-portal",
|
||||
"version": "0.1.0",
|
||||
"dependencies": {
|
||||
"next": "16.4.3",
|
||||
"next": "16.4.6",
|
||||
"next-auth": "5.0.0-beta.32",
|
||||
"react": "19.2.6",
|
||||
"react-dom": "19.2.6",
|
||||
@@ -613,15 +613,15 @@
|
||||
}
|
||||
},
|
||||
"node_modules/@next/env": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/env/-/env-16.4.3.tgz",
|
||||
"integrity": "sha512-a7tz1QCcWWkwC/rPJcPMJk/UNRu9CFhDd3OHYE5hddbJrs8BqRTalxI6GlKCWEGzRLHN+S/B7a4PAHCtm25aBQ==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/env/-/env-16.4.6.tgz",
|
||||
"integrity": "sha512-SunBjJ6t+oBtecS3dTjdVuMhUogP5wD/vrGL5EVuQYM1iS4O5ilL51HkiJ3sPjMzRHiCChvr4dbaSJbR7F3lxA==",
|
||||
"license": "MIT"
|
||||
},
|
||||
"node_modules/@next/swc-darwin-arm64": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-16.4.3.tgz",
|
||||
"integrity": "sha512-4yq5EXBt+VDtAZwTyfijaFp5D2C5oz3Ikw5a2kiX2K9nw72vrZX2q5UuAlkPtUMO1tQz6JTKpaKWjS7OOefTDQ==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-16.4.6.tgz",
|
||||
"integrity": "sha512-kJ4VVZkley17xKaJx72QN2IBqjrj7zenCQZaUF0l9ShS/1Mt2kW4+Z5KGG6vgr3L/J562xTOizVyM1iA/u5nlg==",
|
||||
"cpu": [
|
||||
"arm64"
|
||||
],
|
||||
@@ -635,9 +635,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/@next/swc-darwin-x64": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-darwin-x64/-/swc-darwin-x64-16.4.3.tgz",
|
||||
"integrity": "sha512-1Rvkn/LUhnEF8WxnRkOrqGhbwXui1bkWFxONKIbN+r7C+9KHDSZ+iUoj4CzymVMWUyZIyx9szcb9+kbKhD500A==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-darwin-x64/-/swc-darwin-x64-16.4.6.tgz",
|
||||
"integrity": "sha512-eIPGZIqC+8JKaeZmvnCANJQF4xWkkHqSnAAajtFxgwDMAOnCgxNvP52SeWZ41PyVwoe+Le/NQuZSaQ8j7YshSA==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
@@ -651,9 +651,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/@next/swc-linux-arm64-gnu": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-16.4.3.tgz",
|
||||
"integrity": "sha512-dCKpXErGg3abUM6t5JTJV/ottVBTStJB5lRJTbgdUdQaQ+jNHiK56Hsc0YAEg/rinSh42hYG3HWiYmEMdilnxg==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-16.4.6.tgz",
|
||||
"integrity": "sha512-9nI6O8vvczH2D9ZNdMGqb/3NuT15T9ksOZnAmx9/gjF2cOi74+xxyf1Hk96uIMfm14c9y6wHeBq6SH8g6udvcA==",
|
||||
"cpu": [
|
||||
"arm64"
|
||||
],
|
||||
@@ -670,9 +670,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/@next/swc-linux-arm64-musl": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-16.4.3.tgz",
|
||||
"integrity": "sha512-WwYbhWkhYBvBtib1K4W0kL8MW2snBD2A5b3SN4vPpqalZbZs5+bQ1yzAdepVoOqrFfEW3dmREy4Zs1MrWcrFbw==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-16.4.6.tgz",
|
||||
"integrity": "sha512-7/qPhTxDp2ScluOJOhLuhWmlA17o1yZ0SIgpISBCpBxXgtnK4+KGywBpFkfLPiU1rnSM1faFGzYkH6i7JdTrqA==",
|
||||
"cpu": [
|
||||
"arm64"
|
||||
],
|
||||
@@ -689,9 +689,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/@next/swc-linux-x64-gnu": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-16.4.3.tgz",
|
||||
"integrity": "sha512-QymWvfUwDEC5/lpJOsxX5VAbyoR2D13+2Jsjz4be7gT4LPqEgdpkeLIR/HFfCLgKzoMhpJbp6I/JnogyNZHcaA==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-16.4.6.tgz",
|
||||
"integrity": "sha512-oOpbNa8XOW1qCGd9VvzC4fbkkRxEls7/WI6tz+YHC0xRA7KpV1U7DrAnCPjzVyOk/karzWEepCOcTIDmwK8FwQ==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
@@ -708,9 +708,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/@next/swc-linux-x64-musl": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-16.4.3.tgz",
|
||||
"integrity": "sha512-Vmjd9D7DpA4Vv3cUlr82QWgJD/BQZmns801vtC5VWHg6jCIA4a5vMKpQnfrM2pyCrp2eV0ENdUg4PlN3bAc2Yw==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-16.4.6.tgz",
|
||||
"integrity": "sha512-aM8CZ+OR2EwXaAYw7KGkW2GDmNDsLBIRe1MMRZCJPTdw/xhTD0IMUVO4sf3KqrzuRouGzwwLZn34+gFeVXiUQA==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
@@ -727,9 +727,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/@next/swc-win32-arm64-msvc": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-16.4.3.tgz",
|
||||
"integrity": "sha512-lG1pPdPLk7gTyGb00n5JIMLdBJgjb+UEhSdZvFbhUMg0DyC6z4B7RnpSKF9VCd4imkLObVbXOFA0kFCpw7yFow==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-16.4.6.tgz",
|
||||
"integrity": "sha512-U0p7/tEtqvHX2crhd841CDwKtp5CFkKXVjOhmfccR3Pvp64sj8KBwRqsvltqLOwVBbj0NtkxwXSDpEHYGbxeXQ==",
|
||||
"cpu": [
|
||||
"arm64"
|
||||
],
|
||||
@@ -743,9 +743,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/@next/swc-win32-x64-msvc": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-16.4.3.tgz",
|
||||
"integrity": "sha512-NmQC9RkJdnPXRaMxtkCzobB3teVjqF33oSOnwDfi+XYGWWYpt+xlGK3mtktSKLbdjwaWbJu2OkkMiRFGUUncKg==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-16.4.6.tgz",
|
||||
"integrity": "sha512-3ZG15/5WIdlTQsIEvc9sPTTSL5XFrlLklIKmfF4fwsDnoAhu6NcBDXsk3mbGxNyo6aVLEGex+fHCv2MahY7a9g==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
@@ -889,12 +889,12 @@
|
||||
}
|
||||
},
|
||||
"node_modules/next": {
|
||||
"version": "16.4.3",
|
||||
"resolved": "https://registry.npmjs.org/next/-/next-16.4.3.tgz",
|
||||
"integrity": "sha512-OqxKTGi9u80FydydsMNYNjnuje9Au+kvHlt2GZ//ftdpDHm1dxKqAaENoOOTX5wKzn+9vaKUNIfZeyZUuLhCnA==",
|
||||
"version": "16.4.6",
|
||||
"resolved": "https://registry.npmjs.org/next/-/next-16.4.6.tgz",
|
||||
"integrity": "sha512-QZJiYhaZLJMo2KpkQGQIwvmd79WVsAWeYIU554a8d7zArS3si/IRy3lBNV/rtYhE70oLwdLYhPAXLPx8HwcwtA==",
|
||||
"license": "MIT",
|
||||
"dependencies": {
|
||||
"@next/env": "16.4.3",
|
||||
"@next/env": "16.4.6",
|
||||
"@swc/helpers": "0.5.23",
|
||||
"baseline-browser-mapping": "^2.9.19",
|
||||
"caniuse-lite": "^1.0.30001579",
|
||||
@@ -908,14 +908,14 @@
|
||||
"node": ">=20.9.0"
|
||||
},
|
||||
"optionalDependencies": {
|
||||
"@next/swc-darwin-arm64": "16.4.3",
|
||||
"@next/swc-darwin-x64": "16.4.3",
|
||||
"@next/swc-linux-arm64-gnu": "16.4.3",
|
||||
"@next/swc-linux-arm64-musl": "16.4.3",
|
||||
"@next/swc-linux-x64-gnu": "16.4.3",
|
||||
"@next/swc-linux-x64-musl": "16.4.3",
|
||||
"@next/swc-win32-arm64-msvc": "16.4.3",
|
||||
"@next/swc-win32-x64-msvc": "16.4.3",
|
||||
"@next/swc-darwin-arm64": "16.4.6",
|
||||
"@next/swc-darwin-x64": "16.4.6",
|
||||
"@next/swc-linux-arm64-gnu": "16.4.6",
|
||||
"@next/swc-linux-arm64-musl": "16.4.6",
|
||||
"@next/swc-linux-x64-gnu": "16.4.6",
|
||||
"@next/swc-linux-x64-musl": "16.4.6",
|
||||
"@next/swc-win32-arm64-msvc": "16.4.6",
|
||||
"@next/swc-win32-x64-msvc": "16.4.6",
|
||||
"sharp": "^0.35.5"
|
||||
},
|
||||
"peerDependencies": {
|
||||
|
||||
@@ -13,7 +13,7 @@
|
||||
"typecheck": "tsc --noEmit"
|
||||
},
|
||||
"dependencies": {
|
||||
"next": "16.4.3",
|
||||
"next": "16.4.6",
|
||||
"next-auth": "5.0.0-beta.32",
|
||||
"react": "19.2.6",
|
||||
"react-dom": "19.2.6",
|
||||
|
||||
Reference in new issue
Block a user