← Home

@dr.pogodin/csurf

npm Repository Homepage
12
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

dr.pogodin

Keywords

expresscsrfcsurftokensmiddlewarejavascripttoolsutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:rndm AI (phantom-deps): Runtime dependency for random token generation; stable across versions. ai
phantom-deps phantom-dep:cookie AI (phantom-deps): Core runtime dependency for cookie parsing; stable across versions. ai
phantom-deps phantom-dep:tsscmp AI (phantom-deps): Runtime dependency for timing-safe comparison; stable across versions. ai
phantom-deps phantom-dep:uid-safe AI (phantom-deps): Runtime dependency for safe UID generation; stable across versions. ai
phantom-deps phantom-dep:http-errors AI (phantom-deps): Runtime dependency for HTTP error handling; stable across versions. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): Babel runtime for transpiled code; stable across versions. ai
phantom-deps phantom-dep:cookie-signature AI (phantom-deps): Runtime dependency for cookie signing; stable across versions. ai

Versions (showing 12 of 12)

Version Deps Published
1.16.9 7 / 27
1.16.8 7 / 27
1.16.7 7 / 27
1.16.6 7 / 27
1.16.5 7 / 27
1.16.4 7 / 26
1.16.3 7 / 26
1.16.2 7 / 25
1.16.1 7 / 25
1.16.0 7 / 25
1.15.0 6 / 9
1.14.2 6 / 10

v1.16.9

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.

v1.16.8

1 finding
LOW No provenance attestation provenance

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

v1.16.7

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.

v1.16.6

1 finding
LOW No provenance attestation provenance

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

v1.16.5

1 finding
LOW No provenance attestation provenance

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

v1.16.4

1 finding
LOW No provenance attestation provenance

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

v1.16.3

1 finding
LOW No provenance attestation provenance

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

v1.16.2

1 finding
LOW No provenance attestation provenance

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

v1.16.1

1 finding
LOW No provenance attestation provenance

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

v1.16.0

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.

v1.15.0

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.

v1.14.2

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.