thanhnvandClaude Opus 4.8
664bd1f00c
Physically move the pure-code subtrees out of .specify into the package, leaving compat symlinks at the old .specify/<dir> paths so every existing reference (internal CASAN_HARNESS_ROOT + external CI/docker/mjs) keeps resolving. Runtime state stays put. Moved (git mv): scripts/ tests/ security/ templates/ config/ governance/ memory/ .specify/<dir> -> packages/casan-harness/<dir> (+ .specify/<dir> symlink) Stays in .specify (state/governance/domain, handled later): logs/ agentops/ level5/ init-options.json traceability-map.json Python `.resolve()` self-location followed the compat symlink into packages and lost the app root; generate-casan-demo-context.py, generate-agentops-dashboard.py and dashboard-server.py now walk UP for the `.specify` state marker instead of a fixed parent depth (fixes "missing trace files" in run-casan4). Full gate: PASS=64 FAIL=0 SKIP=3 (CASAN_CI_STEP_TIMEOUT_SEC=1200 — track-a ~450s runs close to the 600s default and can tip over under load; this is timing variance, not a regression — it passed cleanly with headroom). Runtime log/audit artifacts kept unstaged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
18 lines
680 B
Plaintext
18 lines
680 B
Plaintext
# Known-bad / denylisted package identifiers. Format: one entry per line, either
|
|
# a bare name (any version) or name@version for a specific pinned bad release.
|
|
# This is a LOCAL denylist used when no live CVE/OSV scanner is available; a real
|
|
# deployment should also run npm audit / pip-audit / osv-scanner (the gate runs
|
|
# them when present and records tool availability in the report).
|
|
#
|
|
# The entries below are illustrative fixtures (documented malware families /
|
|
# typosquat campaigns) so the gate has deterministic denials to test against.
|
|
event-stream@3.3.6
|
|
flatmap-stream
|
|
coa@2.0.3
|
|
rc@1.2.9
|
|
ua-parser-js@0.7.29
|
|
node-ipc@10.1.1
|
|
colors@1.4.44-liberty-2
|
|
crossenv
|
|
cross-env.js
|