@ember-data/model
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation is the expected pattern for this monorepo's automation migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects ember-data to warp-drive rebranding; resumed publishing under CI automation with provenance attestation. | ai | |
| phantom-deps | phantom-dep:@embroider/macros | AI (phantom-deps): Build-time macro dependency referenced in config; not directly imported at runtime is expected for ember-addon packages. | ai | |
| phantom-deps | phantom-dep:@warp-drive/utilities | AI (phantom-deps): Sibling monorepo package referenced in config files; phantom-dep false positive for this package structure. | ai |
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
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
Published 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.