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>
34 lines
540 B
Plaintext
34 lines
540 B
Plaintext
# Popular package names used for typosquat proximity checks (edit distance <= 1
|
|
# to one of these, but not an exact match, is flagged as a likely typosquat).
|
|
# Extend as the project's real dependency surface grows.
|
|
express
|
|
react
|
|
react-dom
|
|
lodash
|
|
axios
|
|
vite
|
|
tailwindcss
|
|
zod
|
|
prisma
|
|
@prisma/client
|
|
bcrypt
|
|
jsonwebtoken
|
|
class-validator
|
|
class-transformer
|
|
@nestjs/core
|
|
@nestjs/common
|
|
@nestjs/jwt
|
|
@nestjs/swagger
|
|
@tanstack/react-query
|
|
react-router-dom
|
|
react-hook-form
|
|
requests
|
|
flask
|
|
django
|
|
numpy
|
|
pandas
|
|
pytest
|
|
requests-oauthlib
|
|
pyyaml
|
|
cryptography
|