@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, 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): 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 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.21.3 | 18 / 9 | |
| 0.21.2 | 18 / 9 | |
| 0.21.1 | 18 / 9 | |
| 0.21.0 | 18 / 9 | |
| 0.20.0 | 18 / 9 | |
| 0.19.0 | 18 / 8 | |
| 0.18.0 | 18 / 8 | |
| 0.17.1 | 18 / 8 | |
| 0.17.0 | 18 / 8 | |
| 0.16.1 | 18 / 8 | |
| 0.16.0 | 18 / 8 | |
| 0.15.0 | 18 / 8 | |
| 0.14.0 | 18 / 8 | |
| 0.7.32 | 14 / 8 | |
| 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.22 | 14 / 8 | |
| 0.7.19 | 14 / 8 | |
| 0.7.18 | 14 / 8 | |
| 0.7.16 | 14 / 8 | |
| 0.7.15 | 14 / 8 | |
| 0.7.14 | 14 / 8 | |
| 0.7.13 | 14 / 8 | |
| 0.7.12 | 14 / 8 | |
| 0.7.11 | 14 / 8 | |
| 0.7.10 | 14 / 8 | |
| 0.7.9 | 14 / 8 | |
| 0.7.8 | 14 / 8 | |
| 0.7.7 | 14 / 8 | |
| 0.7.6 | 14 / 8 | |
| 0.7.5 | 14 / 8 | |
| 0.7.4 | 14 / 8 | |
| 0.7.3 | 14 / 8 | |
| 0.7.2 | 14 / 8 | |
| 0.7.1 | 14 / 8 | |
| 0.7.0 | 14 / 8 | |
| 0.6.4 | 14 / 8 | |
| 0.6.3 | 14 / 8 | |
| 0.6.2 | 14 / 8 | |
| 0.6.1 | 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 | |
| 0.3.0 | 14 / 8 | |
| 0.2.2 | 14 / 8 | |
| 0.2.1 | 14 / 8 | |
| 0.1.0 | 2 / 6 |
v0.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.