react-virtual
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@scarf/scarf | AI (phantom-deps): Known scarf telemetry package; declared but not imported by design. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Non-fatal optional postinstall script from a well-established, trusted publisher; consistent across versions. | ai | |
| phantom-deps | phantom-dep:ts-toolbelt | AI (phantom-deps): Declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@reach/observe-rect | AI (phantom-deps): Declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.10.4 | 1 / 43 | |
| 2.10.3 | 1 / 43 | |
| 2.10.2 | 1 / 43 | |
| 2.10.0 | 1 / 44 | |
| 2.9.1 | 1 / 43 | |
| 2.9.0 | 1 / 43 | |
| 2.8.2 | 1 / 43 | |
| 2.8.1 | 1 / 43 | |
| 2.8.0 | 1 / 43 | |
| 2.7.2 | 1 / 43 | |
| 2.7.1 | 1 / 43 | |
| 2.7.0 | 2 / 43 | |
| 2.6.2 | 2 / 41 | |
| 2.6.1 | 2 / 41 | |
| 2.6.0 | 2 / 41 | |
| 2.5.0 | 2 / 41 | |
| 2.4.0 | 2 / 41 | |
| 2.3.2 | 2 / 41 | |
| 2.2.5 | 2 / 41 | |
| 2.2.1 | 2 / 41 | |
| 2.1.9 | 3 / 41 | |
| 2.1.7 | 3 / 41 | |
| 2.1.6 | 3 / 41 | |
| 2.1.4 | 3 / 41 | |
| 2.1.2 | 3 / 41 | |
| 2.1.0 | 3 / 41 | |
| 2.0.0 | 3 / 41 |
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.