← Home

@fiscozen/datepicker

npm

Design System Datepicker component

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

panicofralen_fiscozentrebhcbfiscozenfrancivagosergioterrasifiscozen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@fiscozen/icons AI (phantom-deps): Same-org component; likely used transitively or via template/style imports in this Vue component library. ai
phantom-deps phantom-dep:@fiscozen/style AI (phantom-deps): Internal org package; phantom-dep heuristic unreliable for re-exported design system deps. ai
phantom-deps phantom-dep:@fiscozen/button AI (phantom-deps): Internal org package; same reasoning. ai
phantom-deps phantom-dep:@fiscozen/divider AI (phantom-deps): Internal org package; same reasoning. ai
phantom-deps phantom-dep:@fiscozen/composables AI (phantom-deps): Internal org package; same reasoning. ai

Versions (showing 9 of 9)

Version Deps Published
3.1.2 7 / 18
3.1.1 7 / 18
3.1.0 7 / 18
3.0.7 7 / 18
3.0.6 7 / 18
3.0.5 7 / 18
3.0.4 8 / 18
0.1.19 6 / 18
0.1.18 7 / 18

v3.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.