react-native-codegen
⚛️ Code generation tools for React Native
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:@babel/parser | AI (phantom-deps): Declared dep used by compiled output in lib/; not directly imported in scanned source. | ai | |
| provenance | missing-githead | AI (provenance): Transition to react-native-bot CI publishing dropped gitHead; bot has 1394 approved versions. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): react-native-bot is the official React Native automated publisher with extensive track record. | ai | |
| phantom-deps | phantom-dep:nullthrows | AI (phantom-deps): Declared dep used by compiled output in lib/; not directly imported in scanned source. | ai | |
| phantom-deps | phantom-dep:flow-parser | AI (phantom-deps): Declared dep used by compiled output in lib/; not directly imported in scanned source. | ai | |
| phantom-deps | phantom-dep:jscodeshift | AI (phantom-deps): Declared dep used by compiled output in lib/; not directly imported in scanned source. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): react-native-codegen is a known namespace placeholder in the React Native ecosystem; 0.0.0 is intentional, not malicious. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Placeholder package intentionally has no description; stable pattern across all versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require(filename) is expected behavior for a code generation tool that loads schema files by path; not a security risk in this context. | ai | |
| bogus-package | bogus-package | AI (bogus-package): The 'fb' spam flag is a false positive — fb is the official Facebook/Meta npm account. No-keywords is trivial for an established package in the React Native ecosystem. | ai | |
| provenance | publisher-changed | AI (provenance): cipolleschi is a known Meta/React Native contributor; transition from react-native-bot to a human maintainer is a routine and expected change for this package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.72.0 | 4 / 17 | |
| 0.71.6 | 4 / 17 | |
| 0.71.5 | 4 / 17 | |
| 0.71.4 | 4 / 17 | |
| 0.71.3 | 4 / 17 | |
| 0.71.2 | 4 / 17 | |
| 0.71.1 | 4 / 17 | |
| 0.71.0 | 4 / 15 | |
| 0.70.7 | 4 / 15 | |
| 0.70.6 | 4 / 15 | |
| 0.70.5 | 4 / 15 | |
| 0.70.4 | 4 / 15 | |
| 0.70.3 | 4 / 15 | |
| 0.70.2 | 4 / 15 | |
| 0.70.1 | 4 / 15 | |
| 0.70.0 | 4 / 15 | |
| 0.69.2 | 4 / 15 | |
| 0.69.1 | 4 / 15 | |
| 0.69.0 | 4 / 15 | |
| 0.0.18 | 4 / 15 | |
| 0.0.17 | 4 / 15 | |
| 0.0.16 | 4 / 15 | |
| 0.0.15 | 4 / 15 | |
| 0.0.14 | 4 / 15 | |
| 0.0.13 | 4 / 15 | |
| 0.0.12 | 3 / 15 | |
| 0.0.11 | 3 / 15 | |
| 0.0.10 | 3 / 15 | |
| 0.0.9 | 3 / 15 | |
| 0.0.8 | 3 / 15 | |
| 0.0.7 | 3 / 15 | |
| 0.0.6 | 3 / 15 | |
| 0.0.5 | 3 / 14 | |
| 0.0.4 | 3 / 14 | |
| 0.0.2 | 3 / 0 | |
| 0.0.1 | 3 / 0 | |
| 0.0.0 | 0 / 0 |
v0.72.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dmitryrykun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-09-25. This could indicate a legitimate maintainer transition or an account compromise.
v0.71.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-02-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.71.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: react-native-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-02-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.71.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-22. This could indicate a legitimate maintainer transition or an account compromise.
v0.71.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dmitryrykun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cipolleschi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-10-31. This could indicate a legitimate maintainer transition or an account compromise.
v0.71.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dmitryrykun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.7
2 findingsThis version was published by a different npm account than previous versions on 2023-10-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dmitryrykun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dmitryrykun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.70.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cortinico.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cortinico.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cortinico.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-01-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-12-08. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-10-22. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-10-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-10-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.