@sproutsocial/seeds-react-partner-logo
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): Sprout Social org package with consistent publish history; lack of Sigstore attestation is not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-theme | AI (phantom-deps): Same-org dependency used transitively via styled-system/theme integration; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.7.17 | 3 / 8 | |
| 1.7.16 | 3 / 8 | |
| 1.7.15 | 3 / 6 | |
| 1.7.14 | 3 / 6 | |
| 1.7.13 | 3 / 6 | |
| 1.7.8 | 3 / 6 | |
| 1.7.7 | 3 / 6 | |
| 1.7.6 | 3 / 6 | |
| 1.7.5 | 3 / 6 | |
| 1.7.4 | 3 / 6 | |
| 1.7.3 | 3 / 6 | |
| 1.7.2 | 3 / 6 | |
| 1.7.1 | 3 / 6 | |
| 1.7.0 | 3 / 6 | |
| 1.6.2 | 3 / 6 | |
| 1.6.1 | 3 / 6 | |
| 1.6.0 | 3 / 6 | |
| 1.5.1 | 3 / 6 | |
| 1.5.0 | 3 / 6 | |
| 1.4.0 | 3 / 6 | |
| 1.3.8 | 3 / 6 | |
| 1.3.7 | 3 / 6 | |
| 1.3.6 | 3 / 6 | |
| 1.3.5 | 3 / 6 | |
| 1.3.4 | 3 / 6 | |
| 1.3.3 | 3 / 6 | |
| 1.3.2 | 3 / 6 | |
| 1.3.1 | 3 / 6 | |
| 1.3.0 | 3 / 6 | |
| 1.2.1 | 3 / 6 | |
| 1.2.0 | 3 / 6 | |
| 1.1.0 | 3 / 5 |
v1.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.14
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
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.