@mariozechner/jiti
Runtime typescript and ESM support for Node.js (fork with virtualModules support)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Package is a scoped fork of the well-known 'jiti' package; Levenshtein match to 'vite' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Package is a scoped fork of the well-known 'jiti' package; Levenshtein match to 'joi' is a false positive with no impersonation intent. | ai | |
| phantom-deps | phantom-dep:std-env | AI (phantom-deps): std-env is declared as a runtime dependency and likely bundled via rspack; phantom-dep finding is a false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:yoctocolors | AI (phantom-deps): yoctocolors is declared as a runtime dependency and likely bundled via rspack; phantom-dep finding is a false positive for this bundled package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.6.5 | 2 / 35 | |
| 2.6.4 | 2 / 35 | |
| 2.6.3 | 2 / 35 | |
| 2.6.2 | 2 / 35 |
v2.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.