ember-basic-dropdown
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): Moved to GitHub Actions CI publishing with SLSA provenance; legitimate transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Ember v2 addon uses addon-main.cjs; small dist/index.js is normal. cibernox is a known Ember maintainer. | ai | |
| provenance | missing-githead | AI (provenance): Expected when publishing via GitHub Actions; SLSA attestation compensates. | ai | |
| phantom-deps | phantom-dep:ember-element-helper | AI (phantom-deps): Used in templates/config, not direct JS imports; normal for Ember addons. | ai | |
| phantom-deps | phantom-dep:ember-style-modifier | AI (phantom-deps): Used in templates/config, not direct JS imports; normal for Ember addons. | ai | |
| phantom-deps | phantom-dep:ember-truth-helpers | AI (phantom-deps): Used in templates/config, not direct JS imports; normal for Ember addons. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Standard Ember v2 addon build tooling; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@embroider/util | AI (phantom-deps): Referenced in Embroider config files; stable false positive for v2 addons. | ai | |
| provenance | no-provenance | AI (provenance): Long-established Ember addon; lack of provenance is common and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:@embroider/util | AI (dependencies): Part of the official Embroider toolchain; legitimate Ember ecosystem dependency. | ai | |
| dependencies | unvetted-dep:ember-style-modifier | AI (dependencies): Well-known Ember addon for style modifiers; no malicious indicators. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 9.0.0 | 6 / 48 | |
| 8.11.1 | 8 / 35 | |
| 8.11.0 | 8 / 35 | |
| 8.10.0 | 8 / 35 | |
| 8.9.0 | 8 / 35 | |
| 8.8.0 | 8 / 35 | |
| 8.7.0 | 8 / 35 | |
| 8.6.2 | 9 / 35 | |
| 8.6.1 | 9 / 35 | |
| 8.4.0 | 10 / 56 |
v9.0.0
3 findingsThis 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.
This version was published by a different npm account than previous versions on 2026-05-15. 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.
v8.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.11.0
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: mkszepp.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
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: mkszepp.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.0
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: mkszepp.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.