Skip to content

Security: codearchitects/CodeArchitects.EnterprisePlatform.WebStack

Security

SECURITY.md

Security Policy

We take the security of the CodeArchitects Enterprise Platform — WebStack seriously. Thank you for helping keep it and its users safe.

Supported versions

Security fixes are provided for the latest released major version line. All packages in this monorepo share a single version.

Version Supported
21.x
< 21

Reporting a vulnerability

Please do not report security vulnerabilities through public GitHub issues, pull requests, or discussions.

Instead, report them privately through GitHub Security Advisories:

  1. Go to the Security tab of this repository.
  2. Click Report a vulnerability.
  3. Fill in the advisory form with as much detail as possible.

Please include, where possible:

  • The affected package(s) and version(s).
  • A description of the vulnerability and its impact.
  • Steps to reproduce, a proof of concept, or affected source location.
  • Any known mitigations or workarounds.

What to expect

  • Acknowledgement of your report within 3 business days.
  • An initial assessment within 10 business days.
  • We will keep you informed of remediation progress and coordinate a disclosure timeline with you.
  • We support coordinated disclosure: please give us a reasonable opportunity to release a fix before any public disclosure.

We appreciate responsible disclosure and will credit reporters in the release notes unless you prefer to remain anonymous.

Dependency auditing & SBOM

Every push and pull request runs a Security & SBOM job (.github/workflows/ci.yml):

  • Full scan (informational): npm audit over the whole dependency graph, including the build/dev toolchain (Angular CLI dev-server, webpack, karma, esbuild, …). These do not ship to consumers and never fail the build.
  • Gate on shipped dependencies: npm run audit:ci (scripts/check-vulnerabilities.mjs) audits only the production dependency graph — what consumers install — and fails the build on any advisory that is not on the allow-list.
  • SBOM: a CycloneDX SBOM of the shipped dependencies (npm run sbom) is generated and uploaded as a build artifact.

Run the same checks locally:

npm run audit        # production advisories (what ships)
npm run audit:all    # full graph, incl. dev/build tooling
npm run audit:ci     # the CI gate
npm run sbom         # write sbom.json (CycloneDX)

Accepted advisories (allow-list)

The single source of truth is .github/allowed-advisories.txt — one GHSA id per line. Only add an advisory when no fix is available and the risk has been assessed as acceptable, and document the rationale below.

Advisory Package Rationale Review by
(none) Shipped dependencies currently report zero vulnerabilities.

Known / accepted advisories (build & dev toolchain)

npm audit (full graph) reports advisories in the Angular build toolchain (@angular-devkit/build-angular 21.2.x and its transitive dependencies). These are not shipped to consumers — the production audit (npm audit --omit=dev) reports 0 vulnerabilities — and they only affect the local development server / build process. They are therefore not gated by CI and are not listed in .github/allowed-advisories.txt (which covers shipped dependencies only).

As of 2026-07, there is no non-breaking fix on the Angular 21.x line: npm's only suggested remediation is a major downgrade of @angular-devkit/build-angular. These are long-standing, upstream-tracked issues in the Angular CLI (angular/angular-cli#28693, #30122); they will clear when we adopt an Angular CLI release that bumps the affected transitive packages.

Advisory Package (installed) Severity Surface Notes
GHSA-gcq2-9pq2-cxqm, GHSA-64mm-vxmg-q3vj http-proxy-middleware 3.0.5 high dev server dev-proxy only; not used at runtime
webpack-dev-server 5.2.5 moderate dev server local ng serve / karma only
sockjs 0.3.24 moderate dev server via webpack-dev-server
GHSA-w5hq-g745-h8pq uuid 8.3.2 moderate build transitive build tooling
GHSA-4x5r-pxfx-6jf8 @babel/core 7.29.7 low build build-time source maps
GHSA-g7r4-m6w7-qqqr esbuild low dev server Windows dev-server only

Re-verify this table when upgrading the Angular CLI: run npm run audit:all and update or remove entries that upstream has resolved.

There aren't any published security advisories