@basmilius/effects-fireworks
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@basmilius/effects-common | AI (dependencies): Sibling package from the same author/monorepo; expected peer dependency for this package family. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 1 / 3 | |
| 1.5.0 | 1 / 3 | |
| 1.2.1 | 1 / 3 | |
| 1.2.0 | 1 / 3 | |
| 1.1.0 | 2 / 8 | |
| 1.0.3 | 2 / 8 |
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.