extract-comments
Uses esprima to extract line and block comments from a string of JavaScript. Also optionally parses code context (the next line of code after a comment).
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:cr | AI (phantom-deps): cr is a tiny carriage-return utility from the jonschlinkert ecosystem; phantom usage is consistent with it being referenced in backup.js or config rather than index.js. | ai | |
| phantom-deps | phantom-dep:export-files | AI (phantom-deps): export-files is a jonschlinkert utility for file globbing; phantom usage consistent with config/build references rather than direct import in index.js. | ai | |
| phantom-deps | phantom-dep:strip-bom-string | AI (phantom-deps): strip-bom-string is a small text utility; phantom usage consistent with backup.js or config references in this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in a fixture/test file (fixtures/assemble.js), not production code. It loads parser modules from file paths, consistent with the package's purpose. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is explicitly declared as a runtime dependency in package.json; this is a false positive from the phantom-deps analyzer. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a well-known publisher; lack of provenance is common and not a security concern here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 2 / 5 | |
| 1.0.0 | 2 / 5 | |
| 0.10.1 | 4 / 8 | |
| 0.10.0 | 4 / 8 | |
| 0.9.0 | 8 / 6 | |
| 0.8.7 | 8 / 6 | |
| 0.8.6 | 7 / 6 | |
| 0.8.5 | 7 / 6 | |
| 0.8.4 | 7 / 4 | |
| 0.8.3 | 7 / 4 | |
| 0.8.2 | 4 / 4 | |
| 0.8.1 | 4 / 4 | |
| 0.8.0 | 4 / 4 | |
| 0.7.3 | 1 / 3 | |
| 0.7.2 | 1 / 3 | |
| 0.7.1 | 2 / 3 | |
| 0.7.0 | 2 / 3 | |
| 0.6.0 | 2 / 2 | |
| 0.5.1 | 1 / 2 | |
| 0.5.0 | 1 / 2 | |
| 0.4.2 | 4 / 4 | |
| 0.4.1 | 4 / 4 | |
| 0.4.0 | 4 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.0 | 3 / 3 | |
| 0.1.1 | 2 / 4 | |
| 0.1.0 | 1 / 5 |
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.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.4.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.4.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.4.0
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.0
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.