@sproutsocial/seeds-react-card
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 Sprout Social seeds-react-* packages; org-level publishing pattern, not a per-version concern. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.1.46 | 5 / 17 | |
| 1.1.45 | 5 / 17 | |
| 1.1.44 | 5 / 17 | |
| 1.1.43 | 5 / 17 | |
| 1.1.42 | 5 / 17 | |
| 1.1.35 | 5 / 17 | |
| 1.1.34 | 5 / 17 | |
| 1.1.33 | 5 / 17 | |
| 1.1.32 | 5 / 17 | |
| 1.1.31 | 5 / 17 | |
| 1.1.30 | 5 / 17 | |
| 1.1.29 | 5 / 17 | |
| 1.1.28 | 5 / 17 | |
| 1.1.27 | 5 / 17 | |
| 1.1.26 | 5 / 17 | |
| 1.1.24 | 5 / 17 | |
| 1.1.22 | 5 / 17 | |
| 1.1.21 | 5 / 17 | |
| 1.1.20 | 5 / 17 | |
| 1.1.19 | 5 / 17 | |
| 1.1.18 | 5 / 17 | |
| 1.1.17 | 5 / 17 | |
| 1.1.16 | 5 / 17 | |
| 1.1.15 | 5 / 17 | |
| 1.1.14 | 5 / 17 | |
| 1.1.13 | 5 / 17 | |
| 1.1.11 | 4 / 17 | |
| 1.1.10 | 4 / 17 | |
| 1.1.9 | 4 / 17 | |
| 1.1.8 | 4 / 17 | |
| 1.1.7 | 4 / 17 | |
| 1.1.6 | 4 / 17 | |
| 1.1.5 | 4 / 17 | |
| 1.1.4 | 4 / 17 | |
| 1.1.3 | 4 / 17 | |
| 1.1.2 | 4 / 17 | |
| 1.1.1 | 4 / 17 | |
| 1.1.0 | 4 / 17 | |
| 1.0.0 | 4 / 17 |
v1.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.