@vxrn/mdx
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:dist/index.native.js | AI (source-diff): Standard esbuild minified bundle for React Native target; not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/index.native.js | AI (source-diff): Network/exec pattern is from bundled MDX/file-processing deps, not a dropper. | ai | |
| phantom-deps | phantom-dep:shiki | AI (phantom-deps): shiki is a declared dependency used in bundled output; phantom-dep heuristic fires on bundled packages. | ai | |
| typosquat | typosquat.levenshtein:mobx | AI (typosquat): Scoped MDX/Tamagui package; name similarity to mobx is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:esbuild-wasm | AI (phantom-deps): esbuild-wasm is a platform-specific binary dependency; phantom-dep heuristic is expected to fire here. | ai | |
| phantom-deps | phantom-dep:rehype | AI (phantom-deps): rehype is a declared dependency; phantom-dep heuristic fires on bundled packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is a cosmetic gap, not a spam indicator. | ai |
Versions (showing 51 of 262)
| Version | Deps | Published |
|---|---|---|
| 1.17.11 | 20 / 1 | |
| 1.17.10 | 20 / 1 | |
| 1.17.9 | 20 / 1 | |
| 1.17.6 | 20 / 1 | |
| 1.17.5 | 20 / 1 | |
| 1.17.4 | 20 / 1 | |
| 1.17.3 | 20 / 1 | |
| 1.17.2 | 20 / 1 | |
| 1.17.1 | 20 / 1 | |
| 1.17.0 | 20 / 1 | |
| 1.16.12 | 20 / 1 | |
| 1.16.11 | 20 / 1 | |
| 1.16.10 | 20 / 1 | |
| 1.16.9 | 20 / 1 | |
| 1.16.8 | 20 / 1 | |
| 1.16.7 | 20 / 1 | |
| 1.16.6 | 20 / 1 | |
| 1.16.5 | 20 / 1 | |
| 1.16.4 | 20 / 1 | |
| 1.16.3 | 20 / 1 | |
| 1.16.2 | 20 / 1 | |
| 1.16.1 | 20 / 1 | |
| 1.16.0 | 20 / 1 | |
| 1.15.10 | 20 / 1 | |
| 1.15.9 | 20 / 1 | |
| 1.15.8 | 20 / 1 | |
| 1.15.7 | 20 / 1 | |
| 1.15.6 | 20 / 1 | |
| 1.15.5 | 20 / 1 | |
| 1.15.4 | 20 / 1 | |
| 1.15.3 | 20 / 1 | |
| 1.15.2 | 20 / 1 | |
| 1.15.1 | 20 / 1 | |
| 1.15.0 | 20 / 1 | |
| 1.14.5 | 20 / 1 | |
| 1.14.4 | 20 / 1 | |
| 1.14.3 | 20 / 1 | |
| 1.14.2 | 20 / 1 | |
| 1.14.1 | 20 / 1 | |
| 1.14.0 | 20 / 1 | |
| 1.13.7 | 20 / 1 | |
| 1.13.6 | 20 / 1 | |
| 1.13.5 | 20 / 1 | |
| 1.13.4 | 20 / 1 | |
| 1.13.3 | 20 / 1 | |
| 1.13.2 | 20 / 1 | |
| 1.13.1 | 20 / 1 | |
| 1.13.0 | 20 / 1 | |
| 1.12.8 | 20 / 1 | |
| 1.12.7 | 20 / 1 | |
| 1.12.6 | 20 / 1 |
v1.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.