@sproutsocial/seeds-react-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, 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-system-props | AI (phantom-deps): Same-org internal dep; declared in package.json dependencies, stable false positive for this package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.0.43 | 6 / 15 | |
| 1.0.42 | 6 / 15 | |
| 1.0.41 | 6 / 15 | |
| 1.0.40 | 6 / 15 | |
| 1.0.39 | 6 / 15 | |
| 1.0.32 | 6 / 15 | |
| 1.0.31 | 6 / 15 | |
| 1.0.30 | 6 / 15 | |
| 1.0.29 | 6 / 15 | |
| 1.0.28 | 6 / 15 | |
| 1.0.27 | 6 / 15 | |
| 1.0.26 | 6 / 15 | |
| 1.0.25 | 6 / 15 | |
| 1.0.24 | 6 / 15 | |
| 1.0.23 | 6 / 15 | |
| 1.0.21 | 6 / 15 | |
| 1.0.19 | 6 / 15 | |
| 1.0.18 | 6 / 15 | |
| 1.0.17 | 6 / 15 | |
| 1.0.16 | 6 / 15 | |
| 1.0.15 | 6 / 15 | |
| 1.0.14 | 6 / 15 | |
| 1.0.13 | 6 / 15 | |
| 1.0.12 | 6 / 15 | |
| 1.0.11 | 6 / 15 | |
| 1.0.10 | 6 / 15 | |
| 1.0.9 | 6 / 15 | |
| 1.0.8 | 6 / 15 | |
| 1.0.7 | 6 / 15 | |
| 1.0.6 | 6 / 15 | |
| 1.0.5 | 6 / 15 | |
| 1.0.4 | 6 / 15 | |
| 1.0.3 | 6 / 15 | |
| 1.0.2 | 6 / 15 | |
| 1.0.1 | 6 / 15 | |
| 1.0.0 | 6 / 15 |
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.