multilang-extract-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Publisher change is from 2018 and stable for years, not a takeover indicator. | ai | |
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): Standard coverage-report vendored prettify.js, not attacker-injected code. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Well-known utility lib; false-positive-prone heuristic for old CJS packages. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires inside spec/fixtures/assemble.js — a test fixture, not production code; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Old package predating Sigstore provenance; absence is expected and not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 4 / 6 | |
| 0.3.2 | 4 / 6 | |
| 0.3.1 | 4 / 6 | |
| 0.2.2 | 4 / 6 | |
| 0.2.1 | 4 / 6 | |
| 0.2.0 | 4 / 5 | |
| 0.1.2 | 3 / 5 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 3 / 5 |
v0.3.2
2 findingsThis version was published by a different npm account (seancsnyder) than the most recent previously approved version (knappi) on 2019-03-07. It has since remained available on npm for 2694 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsThis version was published by a different npm account (seancsnyder) than the most recent previously approved version (knappi) on 2018-10-23. It has since remained available on npm for 2829 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[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.