← Home

wc-datepicker

npm Repository Homepage
15
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

psiekmann

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/wc-datepicker/p-8644beb7.entry.js AI (source-diff): Stencil.js minified build output; code is readable datepicker logic, no malicious patterns. ai
source-diff obfuscated-file:dist/wc-datepicker/p-94a3030e.entry.js AI (source-diff): Standard Stencil.js minified build output; datepicker logic only, no suspicious behavior. ai
source-diff obfuscated-file:dist/wc-datepicker/p-6029c278.entry.js AI (source-diff): Stencil.js build artifact; minified datepicker logic with no suspicious behavior. ai
source-diff obfuscated-file:dist/wc-datepicker/p-4aacc522.entry.js AI (source-diff): Standard Stencil.js minified build output; content is readable datepicker logic with no malicious patterns. ai
source-diff obfuscated-file:dist/wc-datepicker/p-4f78e8be.js AI (source-diff): Standard Stencil.js minified runtime output; not malicious obfuscation. ai
source-diff obfuscated-file:dist/wc-datepicker/p-5d760970.entry.js AI (source-diff): Standard Stencil.js minified component entry; readable datepicker logic visible in sample. ai

Versions (showing 15 of 15)

Version Deps Published
0.12.0 1 / 15
0.11.0 1 / 15
0.10.0 1 / 15
0.9.5 1 / 15
0.9.4 1 / 15
0.9.3 1 / 15
0.9.2 1 / 15
0.9.1 1 / 15
0.9.0 1 / 15
0.8.1 1 / 15
0.8.0 1 / 15
0.7.0 1 / 15
0.6.0 1 / 15
0.2.0 1 / 15
0.1.0 1 / 15

v0.7.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.

v0.6.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.

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.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.