@sproutsocial/seeds-react-pagination
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 versions of this org's packages; not a per-version risk signal. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-theme | AI (phantom-deps): Same-org scope; likely used transitively or in type declarations rather than direct imports. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-system-props | AI (phantom-deps): Same-org scope; consistent with monorepo peer/type usage pattern. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.1.11 | 5 / 10 | |
| 0.1.10 | 5 / 10 | |
| 0.1.9 | 5 / 10 | |
| 0.1.8 | 5 / 10 | |
| 0.1.4 | 5 / 10 | |
| 0.1.2 | 5 / 10 | |
| 0.1.0 | 5 / 10 |
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.