@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 — the axios compromise (March 2026) relied on exactly this gap.
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 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.