@react-native-windows/codegen
Generators for react-native-codegen targeting react-native-windows
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Missing gitHead is a side effect of the CI/CD pipeline change between Microsoft automation accounts; no malicious signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Both rnbot and microsoft1es are Microsoft-affiliated automation accounts for react-native-windows publishing; this transition is a legitimate internal change, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is an artifact of version series tracking; microsoft1es has a strong track record and the package content is unchanged from prior approved versions. | ai | |
| phantom-deps | phantom-dep:mustache | AI (phantom-deps): mustache is declared in package.json dependencies and used in the compiled output; phantom-dep false positive for TypeScript-compiled packages. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic requires are used to resolve known peer dependency paths (react-native, @react-native/codegen) at runtime — standard pattern for a codegen tool, not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): minimatch is declared in package.json dependencies and used in the compiled output; phantom-dep false positive for TypeScript-compiled packages. | ai | |
| dependencies | unvetted-dep:@react-native-windows/fs | AI (dependencies): First-party sibling package from the same microsoft/react-native-windows monorepo, published by the same microsoft1es account at the same version. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is declared in package.json dependencies and used in the compiled output; phantom-dep false positive for TypeScript-compiled packages. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 0.84.0 | 7 / 15 | |
| 0.83.1 | 7 / 15 | |
| 0.83.0 | 7 / 15 | |
| 0.82.1 | 7 / 15 | |
| 0.82.0 | 7 / 15 | |
| 0.81.6 | 6 / 15 | |
| 0.81.5 | 6 / 15 | |
| 0.81.4 | 6 / 15 | |
| 0.81.3 | 6 / 15 | |
| 0.81.2 | 6 / 15 | |
| 0.81.1 | 6 / 15 | |
| 0.81.0 | 6 / 15 | |
| 0.80.2 | 6 / 15 | |
| 0.80.1 | 6 / 15 | |
| 0.80.0 | 6 / 15 | |
| 0.79.1 | 6 / 15 | |
| 0.79.0 | 6 / 15 | |
| 0.78.3 | 6 / 15 | |
| 0.78.2 | 6 / 15 | |
| 0.78.1 | 6 / 15 | |
| 0.78.0 | 6 / 15 | |
| 0.77.2 | 6 / 15 | |
| 0.77.1 | 6 / 15 | |
| 0.77.0 | 6 / 15 | |
| 0.76.3 | 6 / 15 | |
| 0.76.2 | 6 / 15 | |
| 0.76.1 | 6 / 15 | |
| 0.76.0 | 6 / 15 | |
| 0.75.7 | 6 / 15 | |
| 0.75.6 | 6 / 15 | |
| 0.75.5 | 6 / 15 | |
| 0.75.4 | 6 / 15 | |
| 0.75.3 | 6 / 15 | |
| 0.75.2 | 6 / 15 | |
| 0.75.1 | 6 / 15 | |
| 0.75.0 | 6 / 15 | |
| 0.74.9 | 6 / 15 | |
| 0.74.8 | 6 / 15 | |
| 0.74.7 | 6 / 15 | |
| 0.74.6 | 6 / 15 | |
| 0.74.5 | 6 / 15 | |
| 0.74.4 | 6 / 15 | |
| 0.74.3 | 6 / 15 | |
| 0.74.2 | 6 / 15 | |
| 0.74.1 | 6 / 15 | |
| 0.74.0 | 6 / 15 | |
| 0.73.2 | 6 / 15 | |
| 0.73.1 | 6 / 15 | |
| 0.73.0 | 6 / 15 | |
| 0.72.4 | 6 / 15 | |
| 0.72.3 | 6 / 15 |
v0.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.73.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.