@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ember-click-outside | AI (phantom-deps): Config-only reference typical for ember-addon tooling. | ai | |
| phantom-deps | phantom-dep:@ember/test-waiters | AI (phantom-deps): Config-only reference typical for ember-addon tooling. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): No new suspicious maintainers added, no behavior change in diff. | ai | |
| provenance | missing-githead | AI (provenance): Metadata-only anomaly, no code/script changes, trusted publisher track record. | ai | |
| dependencies | unvetted-peer-dep:ember-source | AI (dependencies): Standard Ember peer dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:ember-test-selectors | AI (dependencies): Well-known Ember testing utility; stable dependency for this addon. | 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 | |
| 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 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 14 / 44 | |
| 4.0.0 | 14 / 44 | |
| 3.0.1 | 13 / 40 | |
| 2.0.17 | 13 / 40 | |
| 2.0.16 | 13 / 40 | |
| 2.0.15 | 13 / 40 | |
| 2.0.11 | 13 / 40 | |
| 2.0.10 | 13 / 40 | |
| 2.0.9 | 13 / 40 | |
| 2.0.8 | 13 / 40 | |
| 2.0.7 | 13 / 40 | |
| 2.0.6 | 13 / 40 | |
| 2.0.5 | 13 / 40 | |
| 2.0.4 | 13 / 40 | |
| 2.0.3 | 13 / 40 |
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (amauryd) than the most recent previously approved version (remadex) on 2026-07-20, but amauryd is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.17
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: remadex.
v2.0.16
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: remadex.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.