@sproutsocial/seeds-react-checkbox
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 | no-provenance | AI (provenance): Consistent across all versions of this org's packages; not a risk indicator for this publisher. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.3.46 | 5 / 5 | |
| 1.3.45 | 5 / 5 | |
| 1.3.44 | 5 / 5 | |
| 1.3.43 | 5 / 5 | |
| 1.3.42 | 5 / 5 | |
| 1.3.41 | 5 / 5 | |
| 1.3.33 | 5 / 5 | |
| 1.3.32 | 5 / 5 | |
| 1.3.31 | 5 / 5 | |
| 1.3.30 | 5 / 5 | |
| 1.3.29 | 5 / 5 | |
| 1.3.28 | 5 / 5 | |
| 1.3.27 | 5 / 5 | |
| 1.3.26 | 5 / 5 | |
| 1.3.25 | 5 / 5 | |
| 1.3.24 | 5 / 5 | |
| 1.3.22 | 5 / 5 | |
| 1.3.20 | 5 / 5 | |
| 1.3.19 | 5 / 5 | |
| 1.3.18 | 5 / 5 | |
| 1.3.17 | 5 / 5 | |
| 1.3.16 | 5 / 5 | |
| 1.3.15 | 5 / 5 | |
| 1.3.14 | 5 / 5 | |
| 1.3.13 | 5 / 5 | |
| 1.3.12 | 5 / 5 | |
| 1.3.11 | 5 / 5 | |
| 1.3.10 | 5 / 5 | |
| 1.3.9 | 5 / 5 | |
| 1.3.8 | 5 / 5 | |
| 1.3.7 | 5 / 5 | |
| 1.3.6 | 5 / 5 | |
| 1.3.5 | 5 / 5 | |
| 1.3.4 | 5 / 5 | |
| 1.3.3 | 5 / 5 | |
| 1.3.2 | 5 / 5 | |
| 1.3.1 | 5 / 5 | |
| 1.3.0 | 5 / 5 | |
| 1.2.0 | 5 / 5 | |
| 1.1.0 | 3 / 6 |
v1.3.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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.
v1.1.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.