@sproutsocial/seeds-react-segmented-control
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sproutsocial/seeds-react-theme | AI (dependencies): Internal @sproutsocial org dependency; same publisher family, stable across versions. | ai | |
| dependencies | unvetted-dep:@sproutsocial/seeds-react-button | AI (dependencies): Internal @sproutsocial org dependency; same publisher family, stable across versions. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-text | AI (phantom-deps): Same-org sibling dep; declared but may be transitively used. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-system-props | AI (phantom-deps): Same-org sibling dep; declared but may be transitively used. Stable false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.1.10 | 7 / 10 | |
| 1.1.9 | 7 / 10 | |
| 1.1.8 | 7 / 10 | |
| 1.1.7 | 7 / 10 | |
| 1.1.6 | 7 / 10 | |
| 1.1.5 | 7 / 10 | |
| 1.1.4 | 7 / 10 | |
| 1.1.3 | 7 / 10 | |
| 1.1.2 | 7 / 10 | |
| 1.1.1 | 7 / 10 | |
| 1.1.0 | 7 / 10 | |
| 1.0.13 | 5 / 10 | |
| 1.0.12 | 5 / 10 | |
| 1.0.11 | 5 / 10 | |
| 1.0.10 | 5 / 10 | |
| 1.0.9 | 5 / 10 | |
| 1.0.8 | 5 / 10 | |
| 1.0.7 | 5 / 10 | |
| 1.0.6 | 5 / 10 | |
| 1.0.5 | 5 / 10 | |
| 1.0.4 | 5 / 10 | |
| 1.0.3 | 5 / 10 | |
| 1.0.2 | 5 / 10 |
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.