parse-comments
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): Publisher change from jonschlinkert to doowb occurred in 2015 (~10 years ago). Both are well-known, prolific npm contributors. This is a stable, legitimate maintainer transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): The added dependency is lodash, one of the most widely used npm packages. No malicious signal; this is a benign utility dependency addition. | ai | |
| dependencies | unvetted-dep:extract-range | AI (dependencies): extract-range is a small utility by the same publisher (jonschlinkert); consistent with their ecosystem of micro-packages. No malicious signals. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4275 days old, predating Sigstore provenance on npm. No provenance is expected and not a risk signal for this established package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 8 / 7 | |
| 0.4.3 | 6 / 2 | |
| 0.4.2 | 6 / 2 | |
| 0.4.1 | 5 / 3 | |
| 0.4.0 | 5 / 3 | |
| 0.3.4 | 4 / 4 | |
| 0.3.3 | 4 / 6 | |
| 0.3.2 | 4 / 7 | |
| 0.3.1 | 5 / 6 | |
| 0.3.0 | 5 / 6 | |
| 0.2.0 | 6 / 6 | |
| 0.1.2 | 5 / 6 | |
| 0.1.1 | 5 / 6 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
2 findingsThis version was published by a different npm account than previous versions on 2015-09-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
2 findingsThis version was published by a different npm account than previous versions on 2015-09-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.