broccoli-middleware
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
jolissreal_aterwjbluekatiegengler
Keywords
builderbuildfrontendbrowserassetpipeline
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): Package publishes via GitHub Actions with SLSA attestation; this is the expected CI/CD pattern for ember-cli org packages. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher with SLSA provenance is a legitimate CI/CD migration for ember-cli org. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is expected when switching to GitHub Actions CI publish flow; SLSA provenance compensates. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance; absence is expected and not a risk signal here. | ai |
v2.1.2
3 findings
HIGH
Missing gitHead — previous versions had it
provenance
This 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.
HIGH
Publisher changed: stefanpenner → GitHub Actions (on 2026-05-09)
provenance
This version was published by a different npm account than previous versions on 2026-05-09. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.