ember-intl
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Well-established package with clean publisher history; single missing gitHead is low risk given no other suspicious signals. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived package with 299 versions; inactivity gap reflects normal release cadence, not account takeover. | ai | |
| phantom-deps | phantom-dep:ember-cli-babel | AI (phantom-deps): Ember convention-loaded package; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:ember-cli-typescript | AI (phantom-deps): Ember convention-loaded package; not directly imported by design. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Config-loading pattern in Ember addon index.js; stable and expected across versions. | ai | |
| phantom-deps | phantom-dep:intl-messageformat | AI (phantom-deps): Referenced in config files per Ember addon conventions; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped package loaded by Ember build pipeline convention. | ai | |
| phantom-deps | phantom-dep:ember-auto-import | AI (phantom-deps): Ember convention-loaded package; not directly imported by design. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 8.2.5 | 3 / 23 | |
| 8.2.4 | 3 / 23 | |
| 8.2.3 | 3 / 23 | |
| 8.2.2 | 3 / 23 | |
| 8.2.1 | 3 / 23 | |
| 8.2.0 | 3 / 23 | |
| 8.1.1 | 3 / 23 | |
| 8.1.0 | 3 / 23 | |
| 8.0.5 | 3 / 23 | |
| 8.0.4 | 3 / 23 | |
| 8.0.3 | 3 / 23 | |
| 8.0.2 | 3 / 23 | |
| 8.0.1 | 3 / 23 | |
| 8.0.0 | 3 / 23 | |
| 7.5.0 | 16 / 34 |
v8.2.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ijlee2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ijlee2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.