@warp-drive/ember
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Signal driven by co-maintainer mass-production heuristic; package is a legitimate Ember addon with proper repo and metadata. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped package @warp-drive/ember is not a typosquat of semver; Levenshtein match is a false positive on the scoped name. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.8.2 | 2 / 23 | |
| 5.8.1 | 2 / 23 | |
| 5.8.0 | 2 / 23 | |
| 5.7.0 | 2 / 23 | |
| 5.6.0 | 2 / 23 |
v5.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.