@enso-ui/inventory
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-dep:@fortawesome/pro-light-svg-icons | AI (dependencies): FontAwesome Pro icons are expected runtime deps for this proprietary Enso UI package. | ai | |
| dependencies | unvetted-dep:@fortawesome/pro-solid-svg-icons | AI (dependencies): FontAwesome Pro icons are expected runtime deps for this proprietary Enso UI package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with private GitLab repo; provenance attestation not expected for this publisher's workflow. | ai | |
| phantom-deps | phantom-dep:v-tooltip | AI (phantom-deps): Vue plugin registered via config, not direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:jsbarcode | AI (phantom-deps): Barcode library likely loaded dynamically or via config; consistent with inventory UI component. | ai | |
| phantom-deps | phantom-dep:@fortawesome/pro-light-svg-icons | AI (phantom-deps): Icon library referenced via config/plugin registration; expected pattern for this UI package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Vue plugin registered via config; not a direct import by design. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.2.9 | 7 / 19 | |
| 5.2.8 | 7 / 19 | |
| 5.2.7 | 7 / 19 | |
| 5.2.6 | 7 / 19 | |
| 5.2.5 | 7 / 19 | |
| 5.2.4 | 7 / 19 |
v5.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.