react-share
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@changesets/cli | AI (phantom-deps): Release tooling dep misplaced in dependencies; not a security concern. | ai | |
| dependencies | unvetted-dep:jsonp | AI (dependencies): jsonp is used legitimately for social share count API calls; stable pattern for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 2 / 29 | |
| 5.2.2 | 2 / 23 | |
| 5.2.1 | 2 / 23 | |
| 5.2.0 | 2 / 23 | |
| 5.1.2 | 2 / 22 | |
| 5.1.1 | 2 / 22 | |
| 5.1.0 | 2 / 22 | |
| 5.0.4 | 2 / 22 | |
| 5.0.3 | 2 / 22 | |
| 5.0.2 | 2 / 22 | |
| 5.0.1 | 2 / 22 | |
| 5.0.0 | 3 / 21 |
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.