broccoli-funnel
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Utility dep likely used indirectly; no malicious install behavior. | ai | |
| phantom-deps | phantom-dep:fast-ordered-set | AI (phantom-deps): Legacy internal dep, stable false positive for this package. | ai | |
| provenance | missing-githead | AI (provenance): gitHead dropped due to CI/CD provenance publishing; provenance attestation supersedes it. | ai | |
| phantom-deps | phantom-dep:walk-sync | AI (phantom-deps): walk-sync is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 7 / 9 | |
| 3.0.8 | 7 / 9 | |
| 3.0.7 | 7 / 9 | |
| 3.0.6 | 7 / 9 | |
| 3.0.5 | 10 / 9 | |
| 3.0.4 | 10 / 9 | |
| 3.0.3 | 10 / 9 | |
| 3.0.2 | 10 / 7 | |
| 3.0.1 | 10 / 7 | |
| 3.0.0 | 12 / 7 |
v4.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (rwjblue) on 2026-07-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.