@sproutsocial/seeds-react-tabs
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 packages consistently lack provenance; stable false positive for this package family. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.4.16 | 3 / 10 | |
| 1.4.15 | 3 / 10 | |
| 1.4.14 | 3 / 10 | |
| 1.4.13 | 3 / 10 | |
| 1.4.12 | 3 / 10 | |
| 1.4.11 | 3 / 10 | |
| 1.3.11 | 3 / 10 | |
| 1.3.10 | 3 / 10 | |
| 1.3.9 | 3 / 10 | |
| 1.3.8 | 3 / 10 | |
| 1.3.7 | 3 / 10 | |
| 1.3.6 | 3 / 10 | |
| 1.3.5 | 3 / 10 | |
| 1.3.4 | 3 / 10 | |
| 1.3.3 | 3 / 10 | |
| 1.3.2 | 3 / 10 | |
| 1.2.9 | 3 / 10 | |
| 1.2.7 | 3 / 10 | |
| 1.2.6 | 3 / 10 | |
| 1.2.5 | 3 / 10 | |
| 1.2.4 | 3 / 10 | |
| 1.2.3 | 3 / 10 | |
| 1.2.2 | 3 / 10 | |
| 1.2.1 | 3 / 10 | |
| 1.2.0 | 3 / 10 | |
| 1.1.12 | 3 / 10 | |
| 1.1.11 | 3 / 10 | |
| 1.1.10 | 3 / 10 | |
| 1.1.9 | 3 / 10 | |
| 1.1.8 | 3 / 10 | |
| 1.1.7 | 3 / 10 | |
| 1.1.6 | 3 / 10 | |
| 1.1.5 | 3 / 10 | |
| 1.1.4 | 3 / 10 | |
| 1.1.3 | 3 / 10 | |
| 1.1.2 | 3 / 10 | |
| 1.1.1 | 3 / 10 | |
| 1.1.0 | 3 / 10 | |
| 1.0.0 | 3 / 10 |
v1.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
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.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.