@elliemae/ds-date-time-picker
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Large monorepo with consistent publish pattern; missing gitHead is a CI environment change, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): Large internal design-system monorepo; provenance not configured org-wide, consistent across all versions. | ai |
Versions (showing 5 of 105)
| Version | Deps | Published |
|---|---|---|
| 3.30.1 | 1 / 3 | |
| 3.30.0 | 1 / 3 | |
| 3.29.1 | 1 / 3 | |
| 3.29.0 | 1 / 3 | |
| 3.27.0 | 1 / 3 |
v3.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.