@sproutsocial/seeds-react-input
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-box | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-text | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.5.32 | 8 / 8 | |
| 1.5.31 | 8 / 8 | |
| 1.5.30 | 8 / 6 | |
| 1.5.29 | 8 / 6 | |
| 1.5.28 | 8 / 6 | |
| 1.5.27 | 8 / 6 | |
| 1.5.26 | 8 / 6 | |
| 1.5.16 | 8 / 6 | |
| 1.5.15 | 8 / 6 | |
| 1.5.14 | 8 / 6 | |
| 1.5.13 | 8 / 6 | |
| 1.5.12 | 8 / 6 | |
| 1.5.11 | 8 / 6 | |
| 1.5.10 | 8 / 6 | |
| 1.5.9 | 8 / 6 | |
| 1.5.8 | 8 / 6 | |
| 1.5.7 | 8 / 6 | |
| 1.5.4 | 8 / 6 | |
| 1.5.2 | 8 / 6 | |
| 1.5.1 | 8 / 6 | |
| 1.5.0 | 8 / 6 | |
| 1.4.20 | 8 / 6 | |
| 1.4.19 | 8 / 6 | |
| 1.4.18 | 8 / 6 | |
| 1.4.17 | 8 / 6 | |
| 1.4.16 | 8 / 6 | |
| 1.4.15 | 8 / 6 | |
| 1.4.14 | 8 / 6 | |
| 1.4.13 | 8 / 6 | |
| 1.4.12 | 8 / 6 | |
| 1.4.11 | 8 / 6 | |
| 1.4.10 | 8 / 6 | |
| 1.4.9 | 8 / 6 | |
| 1.4.8 | 8 / 6 | |
| 1.4.7 | 8 / 6 | |
| 1.4.6 | 8 / 6 | |
| 1.4.5 | 8 / 6 | |
| 1.4.4 | 8 / 6 | |
| 1.4.3 | 8 / 6 | |
| 1.4.2 | 8 / 6 | |
| 1.4.1 | 8 / 6 | |
| 1.4.0 | 8 / 6 | |
| 1.3.2 | 8 / 6 | |
| 1.3.1 | 8 / 6 | |
| 1.3.0 | 8 / 6 | |
| 1.2.0 | 8 / 6 | |
| 1.1.0 | 6 / 7 |
v1.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.