csurf MIT 29 versions

csurf

npm Repository Homepage

CSRF token middleware

29

Versions

MIT

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

defunctzombiedougwilsonfishrock123jongleberrytjholowaychuk

Keywords

csrftokensmiddlewareexpress

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): [email protected] is a legitimate early stub release from a well-established publisher; minimal content is expected for a v0.0.1 initial commit from 2012.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance on npm by many years; absence of attestation is expected and not a risk signal for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from jongleberry to mscdex occurred in 2014 as part of a legitimate Express.js org maintainer transition. mscdex is a highly trusted publisher with 634 approved packages.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): mscdex and fishrock123 are well-known Express.js ecosystem maintainers; this addition in 2014 reflects a legitimate org-level transfer, not a compromise.	ai	2026/04/24

Versions (showing 29 of 29)

Version	Deps	Published
1.11.0	4 / 14	2020-01-19
1.10.0	4 / 14	2019-04-23
1.9.0	4 / 11	2016-05-27
1.8.3	4 / 7	2015-06-11
1.8.2	4 / 7	2015-05-10
1.8.1	4 / 7	2015-05-04
1.8.0	4 / 7	2015-04-08
1.7.0	4 / 7	2015-02-15
1.6.6	4 / 7	2015-02-01
1.6.5	4 / 7	2015-01-09
1.6.4	4 / 7	2014-12-30
1.6.3	4 / 7	2014-11-09
1.6.2	4 / 8	2014-10-14
1.6.1	3 / 8	2014-09-06
1.6.0	3 / 8	2014-09-04
1.5.0	3 / 8	2014-08-24
1.4.1	3 / 8	2014-08-22
1.4.0	3 / 8	2014-07-30
1.3.0	3 / 8	2014-07-04
1.2.2	1 / 7	2014-06-18
1.2.1	1 / 7	2014-06-08
1.2.0	2 / 7	2014-05-13
1.1.0	2 / 6	2014-04-06
1.0.0	1 / 6	2014-03-05
0.1.2	1 / 0	2013-09-03
0.1.1	1 / 0	2013-08-31
0.1.0	0 / 0	2013-08-17
0.0.2	0 / 0	2013-05-21
0.0.1	0 / 0	2013-05-15

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.3

1 finding

LOW No provenance attestation provenance

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

v1.8.2

1 finding

LOW No provenance attestation provenance

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

v1.8.1

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.6

1 finding

LOW No provenance attestation provenance

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

v1.6.5

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.1

2 findings

HIGH Publisher changed: dougwilson → jongleberry (on 2014-08-22) provenance

This version was published by a different npm account than previous versions on 2014-08-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

2 findings

HIGH Publisher changed: jongleberry → dougwilson (on 2014-07-04) provenance

This version was published by a different npm account than previous versions on 2014-07-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

2 findings

HIGH Publisher changed: jongleberry → mscdex (on 2014-05-13) provenance

This version was published by a different npm account than previous versions on 2014-05-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

v0.0.1

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.