@sproutsocial/seeds-react-chart-legend
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sproutsocial/seeds-react-box | AI (dependencies): Internal Sprout Social monorepo sibling dep; expected pattern for this package family. | ai | |
| dependencies | unvetted-dep:@sproutsocial/seeds-react-icon | AI (dependencies): Internal Sprout Social monorepo sibling dep; expected pattern for this package family. | ai | |
| dependencies | unvetted-dep:@sproutsocial/seeds-react-theme | AI (dependencies): Internal Sprout Social monorepo sibling dep; expected pattern for this package family. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.0.45 | 5 / 10 | |
| 1.0.44 | 5 / 10 | |
| 1.0.43 | 5 / 10 | |
| 1.0.42 | 5 / 10 | |
| 1.0.41 | 5 / 10 | |
| 1.0.40 | 5 / 10 | |
| 1.0.32 | 5 / 10 | |
| 1.0.31 | 5 / 10 | |
| 1.0.30 | 5 / 10 | |
| 1.0.29 | 5 / 10 | |
| 1.0.28 | 5 / 10 | |
| 1.0.27 | 5 / 10 | |
| 1.0.26 | 5 / 10 | |
| 1.0.25 | 5 / 10 | |
| 1.0.24 | 5 / 10 | |
| 1.0.23 | 5 / 10 | |
| 1.0.22 | 5 / 10 | |
| 1.0.20 | 5 / 10 | |
| 1.0.19 | 5 / 10 | |
| 1.0.18 | 5 / 10 | |
| 1.0.17 | 5 / 10 | |
| 1.0.16 | 5 / 10 | |
| 1.0.15 | 5 / 10 | |
| 1.0.14 | 5 / 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 | |
| 1.0.1 | 5 / 10 | |
| 1.0.0 | 5 / 10 |
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.