broccoli-debug
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Old, stable maintainer transition to trusted rwjblue; not a fresh compromise signal. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publisher change, analyzer itself notes inconsistency with takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deps are established broccoli-ecosystem packages, consistent with a legitimate rewrite. | ai | |
| phantom-deps | phantom-dep:heimdalljs | AI (phantom-deps): heimdalljs is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:fs-tree-diff | AI (phantom-deps): fs-tree-diff is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:heimdalljs-logger | AI (phantom-deps): heimdalljs-logger is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.6.5 | 6 / 5 | |
| 0.6.4 | 6 / 4 | |
| 0.6.3 | 7 / 4 | |
| 0.6.2 | 7 / 4 | |
| 0.6.1 | 7 / 5 | |
| 0.6.0 | 6 / 5 | |
| 0.1.1 | 1 / 0 | |
| 0.1.0 | 1 / 0 |
v0.6.4
2 findingsThis version was published by a different npm account (rwjblue) than the most recent previously approved version (joliss) on 2017-11-10. It has since remained available on npm for 3175 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
2 findingsThis version was published by a different npm account (rwjblue) than the most recent previously approved version (joliss) on 2017-07-20. It has since remained available on npm for 3288 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
2 findingsThis version was published by a different npm account (rwjblue) than the most recent previously approved version (joliss) on 2017-05-26. It has since remained available on npm for 3343 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
2 findingsThis version was published by a different npm account (rwjblue) than the most recent previously approved version (joliss) on 2017-05-07. It has since remained available on npm for 3362 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsThis version was published by a different npm account (rwjblue) than the most recent previously approved version (joliss) on 2017-05-07. It has since remained available on npm for 3362 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.