@triptyk/ember-ui
User interface components for Ember.js applications
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 |
|---|---|---|---|---|
| dependencies | unvetted-peer-dep:ember-source | AI (dependencies): Standard Ember peer dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:ember-yeti-table | AI (dependencies): Known Ember ecosystem table component; stable dependency for this addon. | ai | |
| dependencies | unvetted-dep:@ember/render-modifiers | AI (dependencies): Official @ember scoped package; stable dependency for this addon. | ai | |
| dependencies | unvetted-dep:ember-test-selectors | AI (dependencies): Well-known Ember testing utility; stable dependency for this addon. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clean history; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:focus-trap | AI (phantom-deps): Ember addon convention; focus-trap is a declared runtime dep used via framework resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:ember-test-selectors | AI (phantom-deps): Ember addon convention; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@ember/string | AI (phantom-deps): Ember addon convention; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped build tool; loaded by Ember/Embroider convention, not direct import. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 13 / 40 | |
| 2.0.15 | 13 / 40 | |
| 2.0.11 | 13 / 40 | |
| 2.0.10 | 13 / 40 | |
| 2.0.8 | 13 / 40 | |
| 2.0.7 | 13 / 40 | |
| 2.0.6 | 13 / 40 | |
| 2.0.5 | 13 / 40 |
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.