js-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:strings | AI (dependencies): strings is a utility dependency consistent with this doc-generation package's purpose; publisher jonschlinkert has a strong track record and the package is 4350 days old with no adverse signals. | ai | |
| phantom-deps | phantom-dep:strip-banner | AI (phantom-deps): strip-banner is a declared dependency by the same author; phantom usage is consistent with config-based or indirect use in a doc-generation tool. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4350 days old, predating Sigstore provenance. Published by well-established maintainer jonschlinkert with strong track record. Absence of provenance is expected and not a risk signal here. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.5.4 | 7 / 3 | |
| 0.5.3 | 7 / 3 | |
| 0.5.2 | 6 / 3 | |
| 0.5.1 | 6 / 3 | |
| 0.5.0 | 6 / 3 | |
| 0.4.2 | 3 / 3 | |
| 0.4.1 | 3 / 3 | |
| 0.4.0 | 3 / 3 | |
| 0.3.9 | 8 / 1 | |
| 0.3.8 | 8 / 1 | |
| 0.3.7 | 8 / 1 | |
| 0.3.6 | 8 / 2 | |
| 0.3.5 | 8 / 2 | |
| 0.3.4 | 9 / 3 | |
| 0.3.3 | 9 / 3 | |
| 0.3.2 | 9 / 3 | |
| 0.3.1 | 9 / 3 | |
| 0.3.0 | 9 / 3 | |
| 0.2.5 | 8 / 4 | |
| 0.2.4 | 8 / 4 | |
| 0.2.3 | 8 / 5 | |
| 0.2.2 | 8 / 5 | |
| 0.2.1 | 8 / 5 | |
| 0.2.0 | 8 / 5 | |
| 0.1.10 | 6 / 3 | |
| 0.1.9 | 6 / 3 | |
| 0.1.8 | 6 / 3 | |
| 0.1.7 | 6 / 3 | |
| 0.1.6 | 6 / 3 | |
| 0.1.5 | 6 / 3 | |
| 0.1.4 | 6 / 3 | |
| 0.1.3 | 6 / 3 | |
| 0.1.2 | 6 / 3 | |
| 0.1.1 | 6 / 3 | |
| 0.1.0 | 6 / 3 |
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[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.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
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.7
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.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.1.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.