react-native-css-interop
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:babel-plugin-tester | AI (dependencies): Legit babel test-tooling dep from trusted publisher; not malicious. | ai | |
| phantom-deps | phantom-dep:babel-plugin-tester | AI (phantom-deps): Used in config, heuristic false positive. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Metro transformer plugin loader pattern; user-supplied config path, not attacker-controlled. Stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; short README and empty sub-entry are structural, not spam indicators. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.2.6 | 6 / 12 | |
| 0.2.5 | 6 / 12 | |
| 0.2.4 | 6 / 12 | |
| 0.2.3 | 6 / 12 | |
| 0.2.2 | 6 / 12 | |
| 0.2.1 | 6 / 12 | |
| 0.2.0 | 6 / 12 | |
| 0.1.22 | 6 / 10 | |
| 0.1.21 | 6 / 10 | |
| 0.1.20 | 6 / 10 | |
| 0.1.19 | 6 / 10 | |
| 0.1.18 | 6 / 10 | |
| 0.1.17 | 6 / 10 | |
| 0.1.16 | 6 / 10 | |
| 0.1.15 | 6 / 10 | |
| 0.1.14 | 6 / 10 | |
| 0.1.13 | 6 / 10 | |
| 0.1.12 | 6 / 10 | |
| 0.1.11 | 6 / 10 | |
| 0.1.10 | 6 / 10 | |
| 0.1.9 | 5 / 10 | |
| 0.1.8 | 5 / 10 | |
| 0.1.7 | 5 / 10 | |
| 0.1.6 | 5 / 10 | |
| 0.1.5 | 5 / 10 | |
| 0.1.4 | 5 / 10 | |
| 0.1.3 | 5 / 10 | |
| 0.1.2 | 5 / 10 | |
| 0.1.1 | 6 / 9 | |
| 0.1.0 | 6 / 9 |
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.