@sproutsocial/seeds-react-menu
Seeds React Menu
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sproutsocial/seeds-react-input | AI (dependencies): First-party Sprout Social seeds-react sibling package; same org, consistent pattern. | ai | |
| dependencies | unvetted-dep:@sproutsocial/seeds-react-button | AI (dependencies): First-party Sprout Social seeds-react sibling package; same org, consistent pattern. | ai | |
| dependencies | unvetted-dep:@sproutsocial/seeds-react-popout | AI (dependencies): First-party Sprout Social seeds-react sibling package; same org, consistent pattern. | ai | |
| dependencies | unvetted-dep:@sproutsocial/seeds-react-token-input | AI (dependencies): First-party Sprout Social seeds-react sibling package; same org, consistent pattern. | ai |
Versions (showing 75 of 75)
| Version | Deps | Published |
|---|---|---|
| 1.13.0 | 20 / 12 | |
| 1.12.3 | 20 / 12 | |
| 1.12.2 | 20 / 12 | |
| 1.12.1 | 20 / 12 | |
| 1.12.0 | 20 / 12 | |
| 1.11.9 | 20 / 12 | |
| 1.11.8 | 20 / 12 | |
| 1.11.7 | 20 / 12 | |
| 1.11.6 | 20 / 12 | |
| 1.11.5 | 20 / 12 | |
| 1.11.4 | 20 / 12 | |
| 1.11.3 | 20 / 12 | |
| 1.11.2 | 20 / 12 | |
| 1.11.1 | 20 / 12 | |
| 1.11.0 | 20 / 12 | |
| 1.10.9 | 19 / 12 | |
| 1.10.8 | 19 / 12 | |
| 1.10.7 | 19 / 12 | |
| 1.10.6 | 19 / 12 | |
| 1.10.5 | 19 / 12 | |
| 1.10.4 | 19 / 12 | |
| 1.10.3 | 19 / 12 | |
| 1.10.2 | 19 / 12 | |
| 1.10.1 | 19 / 12 | |
| 1.10.0 | 19 / 12 | |
| 1.9.2 | 19 / 12 | |
| 1.8.6 | 19 / 12 | |
| 1.8.5 | 19 / 12 | |
| 1.8.4 | 19 / 12 | |
| 1.8.3 | 19 / 12 | |
| 1.8.1 | 19 / 12 | |
| 1.8.0 | 19 / 12 | |
| 1.7.15 | 19 / 12 | |
| 1.7.14 | 19 / 12 | |
| 1.7.13 | 19 / 12 | |
| 1.7.12 | 19 / 12 | |
| 1.7.11 | 19 / 12 | |
| 1.7.10 | 19 / 12 | |
| 1.7.9 | 19 / 12 | |
| 1.7.8 | 19 / 12 | |
| 1.7.7 | 19 / 12 | |
| 1.7.6 | 19 / 12 | |
| 1.7.5 | 19 / 12 | |
| 1.7.2 | 16 / 12 | |
| 1.7.1 | 16 / 12 | |
| 1.7.0 | 16 / 12 | |
| 1.6.17 | 16 / 12 | |
| 1.6.16 | 16 / 12 | |
| 1.6.15 | 16 / 12 | |
| 1.6.14 | 16 / 12 | |
| 1.6.13 | 16 / 12 | |
| 1.6.12 | 16 / 12 | |
| 1.6.11 | 16 / 12 | |
| 1.6.10 | 16 / 12 | |
| 1.6.9 | 16 / 12 | |
| 1.6.8 | 16 / 12 | |
| 1.6.7 | 16 / 12 | |
| 1.6.6 | 15 / 11 | |
| 1.6.5 | 15 / 11 | |
| 1.6.4 | 15 / 11 | |
| 1.6.3 | 15 / 11 | |
| 1.6.2 | 15 / 11 | |
| 1.6.1 | 15 / 11 | |
| 1.6.0 | 15 / 11 | |
| 1.5.2 | 15 / 11 | |
| 1.5.1 | 15 / 11 | |
| 1.5.0 | 15 / 11 | |
| 1.4.1 | 15 / 11 | |
| 1.4.0 | 15 / 11 | |
| 1.3.2 | 15 / 11 | |
| 1.3.1 | 15 / 11 | |
| 1.3.0 | 15 / 11 | |
| 1.2.3 | 15 / 11 | |
| 1.2.2 | 15 / 11 | |
| 1.2.1 | 15 / 11 |
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.