relay-debugger-react-native-runtime
Runtime part 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/index.js | AI (source-diff): lib/index.js is a standard webpack bundle as evidenced by the webpackBootstrap pattern and the package's explicit webpack devDependency and build script. Long lines are webpack output, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Maintainers fb and leebyron are Facebook/Meta and Lee Byron (GraphQL co-creator) — legitimate React/Relay ecosystem publishers. Missing metadata is typical for internal Facebook tooling packages. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() calls are webpack devtool:eval bundle artifacts wrapping standard CommonJS module code — not arbitrary code execution. Stable pattern for this webpack-built package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 0 / 10 | |
| 0.0.9 | 0 / 12 | |
| 0.0.8 | 0 / 12 | |
| 0.0.7 | 0 / 12 | |
| 0.0.6 | 0 / 12 | |
| 0.0.5 | 0 / 12 | |
| 0.0.4 | 0 / 12 | |
| 0.0.3 | 0 / 12 | |
| 0.0.2 | 0 / 12 | |
| 0.0.1 | 0 / 12 |
v0.0.10
2 findingsMatched 4 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: fb, leebyron. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.