@sproutsocial/seeds-react-grid
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Sprout Social seeds monorepo uses 0.0.0 as initial placeholder version; not indicative of malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): Org-published design system component; lack of provenance is common and not a risk indicator here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.2.9 | 3 / 10 | |
| 0.2.8 | 3 / 10 | |
| 0.2.7 | 3 / 10 | |
| 0.2.6 | 3 / 10 | |
| 0.2.5 | 3 / 10 | |
| 0.2.0 | 3 / 10 | |
| 0.1.1 | 3 / 10 | |
| 0.1.0 | 3 / 10 | |
| 0.0.1 | 3 / 10 | |
| 0.0.0 | 3 / 10 |
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.