@companieshouse/web-security-node
Middleware for chs authentication
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:express-async-handler | AI (dependencies): Well-known utility package; stable dependency for this middleware across versions. | ai | |
| dependencies | unvetted-dep:@companieshouse/node-session-handler | AI (dependencies): First-party @companieshouse scoped dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:@companieshouse/structured-logging-node | AI (dependencies): First-party @companieshouse scoped dependency; expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.4.19 | 5 / 19 | |
| 4.4.18 | 5 / 19 | |
| 4.4.17 | 5 / 19 | |
| 4.4.16 | 5 / 19 | |
| 4.4.14 | 5 / 18 | |
| 4.4.13 | 5 / 18 | |
| 4.4.12 | 5 / 18 | |
| 4.4.9 | 5 / 18 |
v4.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.