@sproutsocial/seeds-react-popout
Seeds React Popout
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-button | AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for bundled/re-exported components in monorepo packages. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 2.5.13 | 11 / 14 | |
| 2.5.12 | 11 / 14 | |
| 2.5.11 | 11 / 14 | |
| 2.5.10 | 11 / 14 | |
| 2.5.9 | 11 / 14 | |
| 2.4.38 | 11 / 14 | |
| 2.4.37 | 11 / 14 | |
| 2.4.36 | 11 / 14 | |
| 2.4.35 | 11 / 14 | |
| 2.4.34 | 11 / 14 | |
| 2.4.33 | 10 / 14 | |
| 2.4.32 | 10 / 14 | |
| 2.4.31 | 10 / 14 | |
| 2.4.30 | 10 / 14 | |
| 2.4.29 | 10 / 14 | |
| 2.4.28 | 10 / 14 | |
| 2.4.25 | 10 / 14 | |
| 2.4.24 | 10 / 14 | |
| 2.4.22 | 10 / 14 | |
| 2.4.21 | 10 / 14 | |
| 2.4.20 | 10 / 14 | |
| 2.4.19 | 10 / 14 | |
| 2.4.18 | 10 / 14 | |
| 2.4.17 | 10 / 14 | |
| 2.4.16 | 10 / 14 | |
| 2.4.15 | 10 / 14 | |
| 2.4.14 | 10 / 14 | |
| 2.4.13 | 10 / 14 | |
| 2.4.12 | 10 / 14 | |
| 2.4.11 | 10 / 14 | |
| 2.4.10 | 10 / 14 | |
| 2.4.9 | 10 / 14 | |
| 2.4.8 | 10 / 14 | |
| 2.4.7 | 10 / 14 | |
| 2.4.6 | 9 / 10 | |
| 2.4.5 | 9 / 10 | |
| 2.4.4 | 9 / 10 | |
| 2.4.3 | 9 / 10 | |
| 2.4.2 | 9 / 10 | |
| 2.4.1 | 9 / 10 | |
| 2.4.0 | 9 / 10 | |
| 2.3.0 | 9 / 8 | |
| 2.2.1 | 9 / 8 | |
| 2.1.1 | 9 / 8 | |
| 2.1.0 | 9 / 8 | |
| 2.0.0 | 9 / 8 |
v2.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.