@sproutsocial/seeds-react-numeral
Seeds React Numeral
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): Sprout Social org package with strong approval history; lack of provenance is a process gap, not a security risk here. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-system-props | AI (phantom-deps): Same-org scoped dep; phantom detection likely a false positive for this component library's build setup. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.0.52 | 6 / 10 | |
| 1.0.51 | 6 / 10 | |
| 1.0.50 | 6 / 10 | |
| 1.0.49 | 6 / 10 | |
| 1.0.48 | 6 / 10 | |
| 1.0.47 | 6 / 10 | |
| 1.0.39 | 6 / 10 | |
| 1.0.38 | 6 / 10 | |
| 1.0.37 | 6 / 10 | |
| 1.0.36 | 6 / 10 | |
| 1.0.35 | 6 / 10 | |
| 1.0.34 | 6 / 10 | |
| 1.0.33 | 6 / 10 | |
| 1.0.32 | 6 / 10 | |
| 1.0.31 | 6 / 10 | |
| 1.0.30 | 6 / 10 | |
| 1.0.29 | 6 / 10 | |
| 1.0.26 | 6 / 10 | |
| 1.0.25 | 6 / 10 | |
| 1.0.23 | 6 / 10 | |
| 1.0.22 | 6 / 10 | |
| 1.0.21 | 6 / 10 | |
| 1.0.20 | 6 / 10 | |
| 1.0.19 | 6 / 10 | |
| 1.0.18 | 6 / 10 | |
| 1.0.17 | 6 / 10 | |
| 1.0.16 | 6 / 10 | |
| 1.0.15 | 6 / 10 | |
| 1.0.14 | 6 / 10 | |
| 1.0.13 | 6 / 10 | |
| 1.0.12 | 6 / 10 | |
| 1.0.11 | 6 / 10 | |
| 1.0.10 | 6 / 10 | |
| 1.0.9 | 6 / 10 | |
| 1.0.8 | 6 / 10 | |
| 1.0.7 | 6 / 10 | |
| 1.0.6 | 6 / 10 | |
| 1.0.5 | 6 / 10 | |
| 1.0.4 | 6 / 10 | |
| 1.0.3 | 6 / 10 | |
| 1.0.2 | 6 / 10 | |
| 1.0.1 | 6 / 10 | |
| 1.0.0 | 6 / 10 |
v1.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.