← Home

csp_evaluator

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

google-wombot

Keywords

cspcontent security policycontent-security-policycsp-evaluator

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:dist/checks/security_checks.js AI (source-diff): Standard TS-compiled CSP checker referencing URL patterns; not actual network+exec. ai
source-diff large-new-source-files AI (source-diff): Compiled TS dist/ output added; matches repo structure of google/csp-evaluator. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.8 0 / 3
1.1.7 0 / 3
1.1.6 0 / 3
1.1.5 0 / 3

v1.1.8

2 findings
HIGH New file with network + code execution: dist/checks/security_checks.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.