@sproutsocial/seeds-react-data-viz
Seeds React Data Viz Components
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): Internal org package; provenance not yet adopted by this publisher's pipeline. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sprout Social internal design system package; missing repo/keywords is a consistent org-wide pattern, not spam. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-dataviz | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic unreliable for internal design system deps. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-partner-logo | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic unreliable for internal design system deps. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-system-props | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic unreliable for internal design system deps. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.7.31 | 14 / 8 | |
| 0.7.30 | 14 / 8 | |
| 0.7.29 | 14 / 8 | |
| 0.7.28 | 14 / 8 | |
| 0.7.27 | 14 / 8 | |
| 0.7.26 | 14 / 8 | |
| 0.7.25 | 14 / 8 | |
| 0.7.24 | 14 / 8 | |
| 0.7.23 | 14 / 8 | |
| 0.7.19 | 14 / 8 | |
| 0.7.18 | 14 / 8 | |
| 0.7.15 | 14 / 8 | |
| 0.7.13 | 14 / 8 | |
| 0.7.11 | 14 / 8 | |
| 0.7.9 | 14 / 8 | |
| 0.7.8 | 14 / 8 | |
| 0.7.7 | 14 / 8 | |
| 0.7.5 | 14 / 8 | |
| 0.7.3 | 14 / 8 | |
| 0.7.1 | 14 / 8 | |
| 0.6.4 | 14 / 8 | |
| 0.6.3 | 14 / 8 | |
| 0.6.0 | 14 / 8 | |
| 0.5.3 | 14 / 8 | |
| 0.5.2 | 14 / 8 | |
| 0.5.1 | 14 / 8 | |
| 0.5.0 | 14 / 8 | |
| 0.4.3 | 14 / 8 | |
| 0.4.2 | 14 / 8 | |
| 0.4.1 | 14 / 8 | |
| 0.4.0 | 14 / 8 | |
| 0.3.1 | 14 / 8 |
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.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.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.