@peerbit/react
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:@chainsafe/libp2p-yamux | AI (phantom-deps): Declared dependency; referenced in config, legitimate usage pattern. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React library; react-dom is a standard peer/dependency for React packages. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): Declared dependency; phantom-dep heuristic does not block usage patterns. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped type package; loaded by convention in React projects. | ai | |
| phantom-deps | phantom-dep:react-router | AI (phantom-deps): Declared dependency; referenced in config, legitimate usage pattern. | ai | |
| phantom-deps | phantom-dep:@libp2p/webrtc | AI (phantom-deps): Declared dependency; referenced in config, legitimate usage pattern. | ai | |
| phantom-deps | phantom-dep:path-browserify | AI (phantom-deps): Declared dependency; referenced in config, legitimate usage pattern. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Framework-scoped type package; loaded by convention in React projects. | ai | |
| phantom-deps | phantom-dep:@libp2p/interface | AI (phantom-deps): @libp2p/interface is a declared peer/type dependency used in config; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of Sigstore provenance is consistent across all versions and not a security signal here. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 1.1.23 | 20 / 13 | |
| 1.1.22 | 20 / 13 | |
| 1.1.21 | 20 / 13 | |
| 1.1.20 | 20 / 13 | |
| 1.1.19 | 20 / 13 | |
| 1.1.18 | 20 / 13 | |
| 1.1.17 | 20 / 13 | |
| 1.1.16 | 20 / 13 | |
| 1.1.15 | 20 / 13 | |
| 1.1.14 | 20 / 13 | |
| 1.1.13 | 20 / 13 | |
| 1.1.12 | 20 / 13 | |
| 1.1.11 | 20 / 13 | |
| 1.1.10 | 20 / 13 | |
| 1.1.9 | 20 / 13 | |
| 1.1.8 | 20 / 13 | |
| 1.1.7 | 20 / 13 | |
| 1.1.6 | 20 / 13 | |
| 1.1.5 | 20 / 13 | |
| 1.1.4 | 18 / 13 | |
| 1.1.3 | 18 / 13 | |
| 1.1.2 | 18 / 13 | |
| 1.1.1 | 18 / 13 | |
| 1.1.0 | 18 / 13 | |
| 1.0.11 | 18 / 11 | |
| 1.0.10 | 18 / 11 | |
| 1.0.9 | 18 / 11 | |
| 1.0.8 | 18 / 11 | |
| 1.0.7 | 18 / 10 | |
| 1.0.6 | 18 / 10 | |
| 1.0.5 | 18 / 10 | |
| 1.0.4 | 18 / 10 | |
| 1.0.3 | 18 / 10 | |
| 1.0.2 | 18 / 10 | |
| 1.0.0 | 18 / 10 | |
| 0.2.3 | 18 / 10 | |
| 0.2.2 | 18 / 10 | |
| 0.2.1 | 18 / 10 | |
| 0.2.0 | 18 / 10 | |
| 0.1.0 | 18 / 10 | |
| 0.0.49 | 18 / 10 | |
| 0.0.48 | 18 / 10 | |
| 0.0.47 | 18 / 10 | |
| 0.0.46 | 18 / 10 | |
| 0.0.45 | 17 / 10 | |
| 0.0.44 | 17 / 10 | |
| 0.0.43 | 17 / 10 | |
| 0.0.42 | 17 / 10 | |
| 0.0.41 | 17 / 10 | |
| 0.0.40 | 17 / 10 | |
| 0.0.39 | 17 / 10 |
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
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.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.
v0.1.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.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.