@enso-ui/select
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:@enso-ui/dropdown-indicator | AI (dependencies): Same org scope (@enso-ui); consistent with the package's established dependency pattern across 135 versions. | ai | |
| provenance | no-provenance | AI (provenance): Established enso-ui org package; lack of provenance is consistent across all versions and not a security risk here. | ai | |
| phantom-deps | phantom-dep:@enso-ui/dropdown | AI (phantom-deps): Same-org sibling dep; phantom detection is a known false positive for this package family. | ai | |
| phantom-deps | phantom-dep:bulma | AI (phantom-deps): CSS framework declared as dep but used via config/build; stable false positive for this UI package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/directives | AI (phantom-deps): Same-org sibling dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/search-mode | AI (phantom-deps): Same-org sibling dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/dropdown-indicator | AI (phantom-deps): Same-org sibling dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer dep for a Vue component library; not directly imported in source is expected. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Config-file reference; stable pattern for this UI library. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Config-file reference; stable pattern for this UI library. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Config-file reference; stable pattern for this UI library. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Config-file reference; stable pattern for this UI library. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.1.16 | 4 / 6 | |
| 4.1.15 | 4 / 6 | |
| 4.1.13 | 4 / 6 | |
| 4.1.12 | 4 / 6 | |
| 4.1.11 | 4 / 6 | |
| 4.1.10 | 4 / 6 | |
| 4.1.9 | 4 / 6 | |
| 4.1.8 | 4 / 6 | |
| 4.1.7 | 4 / 6 | |
| 4.1.6 | 4 / 6 | |
| 4.1.5 | 4 / 6 | |
| 4.1.4 | 4 / 6 | |
| 4.1.3 | 8 / 2 | |
| 4.1.2 | 10 / 0 | |
| 4.1.1 | 10 / 0 | |
| 4.1.0 | 10 / 0 | |
| 4.0.0 | 10 / 0 |
v4.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.