@sproutsocial/seeds-react-modal
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dnd | AI (phantom-deps): react-dnd is a declared runtime dep referenced in config files; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-dnd-html5-backend | AI (phantom-deps): react-dnd-html5-backend is a declared runtime dep referenced in config files; same false-positive pattern as react-dnd. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 2.5.9 | 13 / 14 | |
| 2.5.8 | 13 / 14 | |
| 2.5.7 | 13 / 14 | |
| 2.5.6 | 13 / 14 | |
| 2.5.5 | 13 / 14 | |
| 2.5.4 | 13 / 14 | |
| 2.5.3 | 13 / 14 | |
| 2.5.2 | 13 / 14 | |
| 2.5.1 | 13 / 14 | |
| 2.5.0 | 13 / 14 | |
| 2.4.9 | 13 / 14 | |
| 2.4.8 | 13 / 14 | |
| 2.4.7 | 13 / 14 | |
| 2.4.5 | 12 / 14 | |
| 2.4.4 | 12 / 14 | |
| 2.4.3 | 12 / 14 | |
| 2.4.2 | 12 / 14 | |
| 2.4.1 | 12 / 14 | |
| 2.4.0 | 12 / 14 | |
| 2.3.0 | 12 / 14 | |
| 2.2.5 | 12 / 14 | |
| 2.2.4 | 12 / 14 | |
| 2.2.3 | 12 / 14 | |
| 2.2.2 | 12 / 14 | |
| 2.2.1 | 12 / 14 | |
| 2.2.0 | 12 / 14 | |
| 2.1.2 | 12 / 14 | |
| 2.1.1 | 12 / 14 | |
| 2.1.0 | 12 / 14 | |
| 2.0.2 | 12 / 14 | |
| 2.0.1 | 12 / 14 | |
| 2.0.0 | 12 / 14 | |
| 1.1.1 | 11 / 14 |
v2.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
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.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.