@sproutsocial/seeds-react-drawer
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): @react-spring/web is a widely-used, legitimate animation library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Sprout Social org package with consistent publish history; lack of Sigstore provenance is a process gap, not a security risk here. | ai | |
| phantom-deps | phantom-dep:@sproutsocial/seeds-react-theme | AI (phantom-deps): Same-org dependency; phantom-dep heuristic false positive for this package's structure. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 2.2.12 | 11 / 10 | |
| 2.2.11 | 11 / 10 | |
| 2.2.10 | 11 / 10 | |
| 2.2.9 | 11 / 10 | |
| 2.2.8 | 11 / 10 | |
| 2.2.7 | 11 / 10 | |
| 1.2.11 | 10 / 10 | |
| 1.2.10 | 10 / 10 | |
| 1.2.9 | 10 / 10 | |
| 1.2.8 | 10 / 10 | |
| 1.2.7 | 10 / 10 | |
| 1.2.6 | 10 / 10 | |
| 1.2.5 | 10 / 10 | |
| 1.2.4 | 10 / 10 | |
| 1.2.3 | 10 / 10 | |
| 1.2.2 | 10 / 10 | |
| 1.1.22 | 10 / 10 | |
| 1.1.20 | 10 / 10 | |
| 1.1.19 | 10 / 10 | |
| 1.1.18 | 10 / 10 | |
| 1.1.17 | 10 / 10 | |
| 1.1.16 | 10 / 10 | |
| 1.1.15 | 10 / 10 | |
| 1.1.14 | 10 / 10 | |
| 1.1.13 | 10 / 10 | |
| 1.1.12 | 10 / 10 | |
| 1.1.11 | 10 / 10 | |
| 1.1.9 | 10 / 10 | |
| 1.1.8 | 10 / 10 | |
| 1.1.5 | 10 / 10 | |
| 1.1.2 | 10 / 10 | |
| 1.1.0 | 10 / 10 | |
| 1.0.3 | 10 / 10 | |
| 1.0.2 | 10 / 10 | |
| 1.0.1 | 10 / 10 | |
| 1.0.0 | 10 / 10 |
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
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.