@enso-ui/datepicker
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:bulma | AI (dependencies): bulma is a well-known CSS framework; its use as a UI dependency is expected for this component library. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): vue is a peer dependency for a Vue component library; not directly imported is expected. | ai | |
| phantom-deps | phantom-dep:bulma | AI (phantom-deps): CSS framework referenced in config/styles, not JS imports; expected pattern. | ai | |
| phantom-deps | phantom-dep:pinia | AI (phantom-deps): State management peer dep for Vue ecosystem; config-only reference is expected. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Declared dependency; referenced in config files as expected for Vue component. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Declared dependency; referenced in config files as expected for Vue component. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Declared dependency; referenced in config files as expected for Vue component. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.1.4 | 4 / 7 | |
| 3.1.3 | 4 / 7 | |
| 3.1.2 | 4 / 3 | |
| 3.1.1 | 4 / 3 | |
| 3.1.0 | 7 / 0 | |
| 3.0.0 | 7 / 0 |
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.