@enso-ui/calendar
Calendar page modules and event-management components for Enso UI.
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:@enso-ui/transitions | AI (phantom-deps): Same-org dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@enso-ui/filters | AI (phantom-deps): Same-org dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@enso-ui/datepicker | AI (phantom-deps): Same-org dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer/config dependency for this Vue component package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@enso-ui/ui | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/forms | AI (phantom-deps): Same-org dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@enso-ui/modal | AI (phantom-deps): Same-org dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@enso-ui/select | AI (phantom-deps): Same-org dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): FontAwesome Vue adapter used via config/template in Vue SFCs; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vue-cal | AI (phantom-deps): vue-cal is a declared runtime dep used via config/template references in a Vue component library; not a direct JS import. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.1.9 | 4 / 14 | |
| 5.1.8 | 4 / 14 | |
| 5.1.7 | 4 / 14 | |
| 5.1.6 | 4 / 14 | |
| 5.1.5 | 4 / 14 | |
| 5.1.4 | 4 / 9 | |
| 5.1.3 | 4 / 9 | |
| 5.1.2 | 11 / 2 | |
| 5.1.1 | 13 / 0 | |
| 5.1.0 | 13 / 0 | |
| 5.0.8 | 13 / 9 | |
| 5.0.7 | 13 / 9 | |
| 5.0.6 | 13 / 9 |
v5.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.