nitrogen
The code-generator for react-native-nitro-modules.
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Benign bun build step with || exit 0 fallback; consistent with this code-generator package's documented build flow. | ai | |
| bogus-package | bogus-package | AI (bogus-package): mrousavy is the legitimate author of the nitro ecosystem; templated naming reflects a real monorepo, not spam. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.35.8 | 5 / 1 | |
| 0.35.7 | 5 / 1 | |
| 0.35.6 | 5 / 1 | |
| 0.35.5 | 5 / 1 | |
| 0.35.4 | 5 / 1 | |
| 0.35.3 | 5 / 1 | |
| 0.35.2 | 5 / 1 | |
| 0.35.1 | 5 / 1 | |
| 0.35.0 | 5 / 1 | |
| 0.34.1 | 5 / 1 | |
| 0.34.0 | 5 / 1 | |
| 0.33.9 | 5 / 1 | |
| 0.33.8 | 5 / 1 | |
| 0.33.7 | 5 / 1 | |
| 0.33.6 | 5 / 1 | |
| 0.33.5 | 5 / 1 | |
| 0.33.4 | 5 / 1 | |
| 0.33.3 | 5 / 1 | |
| 0.33.2 | 5 / 1 | |
| 0.33.1 | 5 / 1 | |
| 0.33.0 | 5 / 1 | |
| 0.32.2 | 5 / 1 | |
| 0.32.1 | 5 / 1 | |
| 0.32.0 | 5 / 1 | |
| 0.31.10 | 5 / 1 | |
| 0.31.9 | 5 / 1 | |
| 0.31.8 | 5 / 1 | |
| 0.31.7 | 5 / 1 | |
| 0.31.6 | 5 / 1 | |
| 0.31.5 | 5 / 1 | |
| 0.29.4 | 5 / 1 |
v0.35.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.10
2 findingsScript: bun build || exit 0;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.9
2 findingsScript: bun build || exit 0;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.8
2 findingsScript: bun build || exit 0;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.7
2 findingsScript: bun build || exit 0;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.6
2 findingsScript: bun build || exit 0;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.5
2 findingsScript: bun build || exit 0;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.