csrf
primary logic behind csrf tokens
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transfer to jongleberry (Jonathan Ong), prolific Express/pillarjs ecosystem maintainer, in 2014. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jongleberry is the package author and a well-established npm maintainer in the pillarjs org. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2014, predates Sigstore provenance infrastructure. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 3 / 12 | |
| 3.0.6 | 3 / 8 | |
| 3.0.5 | 4 / 8 | |
| 3.0.4 | 4 / 7 | |
| 3.0.3 | 4 / 7 | |
| 3.0.2 | 4 / 7 | |
| 3.0.1 | 4 / 3 | |
| 3.0.0 | 4 / 3 | |
| 2.0.7 | 4 / 3 | |
| 2.0.6 | 4 / 3 | |
| 2.0.5 | 4 / 3 | |
| 2.0.4 | 4 / 3 | |
| 2.0.3 | 4 / 3 | |
| 2.0.2 | 4 / 3 | |
| 2.0.1 | 4 / 3 | |
| 0.0.3 | 2 / 1 | |
| 0.0.2 | 1 / 1 | |
| 0.0.1 | 2 / 0 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsThis version was published by a different npm account than previous versions on 2015-01-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsThis version was published by a different npm account than previous versions on 2014-12-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2014-11-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.