@enso-ui/quick-view
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bulma | AI (phantom-deps): bulma is a CSS framework referenced in config/build files; not directly imported in JS is expected for this package type. | ai | |
| phantom-deps | phantom-dep:@enso-ui/ui | AI (phantom-deps): Same-org peer dependency; phantom-dep false positive for intra-org packages. | ai | |
| phantom-deps | phantom-dep:@enso-ui/transitions | AI (phantom-deps): Same-org sibling dep; phantom-dep false positive for intra-org packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.2.9 | 0 / 4 | |
| 3.2.8 | 0 / 4 | |
| 3.2.6 | 0 / 4 | |
| 3.2.4 | 0 / 4 | |
| 3.2.3 | 0 / 4 | |
| 3.2.2 | 2 / 2 | |
| 3.2.1 | 4 / 0 | |
| 3.2.0 | 4 / 0 | |
| 3.1.0 | 4 / 0 |
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.