Skip to content

security: add disclosure policy, threat model, and CI audit gate - #164

Merged
teamchong merged 4 commits into
teamchong:mainfrom
mkhalid-s:security/repository-hardening
Aug 6, 2026
Merged

teamchong merged 4 commits into
teamchong:mainfrom
mkhalid-s:security/repository-hardening

Conversation

@mkhalid-s

Copy link
Copy Markdown
Contributor

Summary

  • add a private vulnerability disclosure policy and publish it with the npm package
  • document assets, trust boundaries, deployment assumptions, residual risks, and a security-review checklist
  • make high-severity dependency auditing an explicit CI gate
  • add Worker authentication regression coverage for fail-closed configuration, invalid callers, and secret stripping
  • create export artifacts with owner-only permissions on POSIX systems

Validation

  • pnpm run audit — no known vulnerabilities
  • pnpm test — 923 tests passed
  • pnpm run typecheck
  • pnpm run build
  • npm pack dry-run includes SECURITY.md and docs/SECURITY_MODEL.md
  • focused secret scan found no credential-shaped secrets in production source, workflows, scripts, or documentation

The branch was rebased onto current main; dependency and Node telemetry hardening already landed upstream were deliberately removed from this PR to avoid duplication.

@mkhalid-s

Copy link
Copy Markdown
Contributor Author

@teamchong This security-hardening PR is rebased onto current main, mergeable, and green (923 local tests plus GitHub CI). It avoids duplicating the dependency and telemetry fixes already landed upstream. Ready for maintainer review when convenient.

`pnpm audit --audit-level high` fails on advisories anywhere in the
tree, including devDependencies. It is red today on
wrangler > miniflare > undici (GHSA-4cwx-7wf7-3272) — build tooling
that never reaches a user's machine — so the gate would block a
release over something the release cannot expose.

pxpipe ships one runtime dependency, gpt-tokenizer. Scoping to --prod
makes a failure mean something precise and worth stopping for: a
dependency we ship has a high-severity advisory. Unscoped, the gate
fires on churn nobody here can act on, gets muted, and takes the real
signal with it.

Toolchain risk stays covered by Dependabot and lockfile review (teamchong#169).
@teamchong

Copy link
Copy Markdown
Owner

Thanks @mkhalid-s

@teamchong
teamchong merged commit 4778577 into teamchong:main Aug 6, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants