@sproutsocial/seeds-react-token-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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Sprout Social org package; lack of provenance is consistent across all their releases. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 1.4.54 | 8 / 11 | |
| 1.4.53 | 8 / 11 | |
| 1.4.52 | 8 / 11 | |
| 1.4.51 | 8 / 11 | |
| 1.4.50 | 8 / 11 | |
| 1.4.49 | 8 / 11 | |
| 1.4.48 | 8 / 11 | |
| 1.4.38 | 8 / 11 | |
| 1.4.37 | 8 / 11 | |
| 1.4.36 | 8 / 11 | |
| 1.4.35 | 8 / 11 | |
| 1.4.34 | 8 / 11 | |
| 1.4.33 | 8 / 11 | |
| 1.4.32 | 8 / 11 | |
| 1.4.31 | 8 / 11 | |
| 1.4.30 | 8 / 11 | |
| 1.4.29 | 8 / 11 | |
| 1.4.28 | 8 / 11 | |
| 1.4.25 | 8 / 11 | |
| 1.4.23 | 8 / 11 | |
| 1.4.22 | 8 / 11 | |
| 1.4.21 | 8 / 11 | |
| 1.4.20 | 8 / 11 | |
| 1.4.19 | 8 / 11 | |
| 1.4.18 | 8 / 11 | |
| 1.4.17 | 8 / 11 | |
| 1.4.16 | 8 / 11 | |
| 1.4.15 | 8 / 11 | |
| 1.4.14 | 8 / 11 | |
| 1.4.13 | 8 / 11 | |
| 1.4.12 | 8 / 11 | |
| 1.4.11 | 8 / 11 | |
| 1.4.10 | 8 / 11 | |
| 1.4.9 | 8 / 11 | |
| 1.4.8 | 8 / 11 | |
| 1.4.7 | 8 / 11 | |
| 1.4.6 | 8 / 11 | |
| 1.4.5 | 8 / 11 | |
| 1.4.4 | 8 / 11 | |
| 1.4.3 | 8 / 11 | |
| 1.4.2 | 8 / 11 | |
| 1.4.1 | 8 / 11 | |
| 1.4.0 | 8 / 11 | |
| 1.3.0 | 8 / 11 | |
| 1.2.0 | 8 / 11 | |
| 1.1.0 | 8 / 11 | |
| 1.0.2 | 8 / 11 | |
| 1.0.1 | 8 / 11 | |
| 1.0.0 | 8 / 11 |
v1.4.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.