virtua
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Legitimate long-running package; 0.0.0 was its actual first version, not a throwaway pattern. | ai | |
| source-diff | obfuscated-file:lib/core/index.mjs | AI (source-diff): Terser-minified rollup build output for new unstable_core export; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/core/index.js | AI (source-diff): Minified rollup/terser build output, not obfuscation; stable for this build-tool-produced library. | ai | |
| source-diff | obfuscated-file:lib/svelte/core.js | AI (source-diff): Minified rollup/terser build output for the Svelte entry; no malicious behavior. | ai | |
| source-diff | obfuscated-file:lib/core/index.cjs | AI (source-diff): Minified rollup+terser output; stable pattern for this package across all versions. | ai | |
| source-diff | obfuscated-file:lib/vue/index.cjs | AI (source-diff): Minified rollup+terser output; stable pattern for this package across all versions. | ai | |
| source-diff | obfuscated-file:lib/solid/index.cjs | AI (source-diff): Minified rollup+terser output; stable pattern for this package across all versions. | ai | |
| source-diff | obfuscated-file:lib/index.cjs | AI (source-diff): Minified rollup+terser output; stable pattern for this package across all versions. | ai |
Versions (showing 94 of 194)
| Version | Deps | Published |
|---|---|---|
| 0.27.5 | 0 / 72 | |
| 0.27.4 | 0 / 72 | |
| 0.27.3 | 0 / 72 | |
| 0.27.2 | 0 / 72 | |
| 0.27.1 | 0 / 72 | |
| 0.27.0 | 0 / 70 | |
| 0.26.0 | 0 / 70 | |
| 0.25.0 | 0 / 69 | |
| 0.24.0 | 0 / 69 | |
| 0.23.3 | 0 / 69 | |
| 0.23.2 | 0 / 69 | |
| 0.23.1 | 0 / 69 | |
| 0.23.0 | 0 / 69 | |
| 0.22.1 | 0 / 63 | |
| 0.22.0 | 0 / 63 | |
| 0.21.1 | 0 / 61 | |
| 0.21.0 | 0 / 61 | |
| 0.20.5 | 0 / 59 | |
| 0.20.4 | 0 / 59 | |
| 0.20.3 | 0 / 59 | |
| 0.20.2 | 0 / 59 | |
| 0.20.1 | 0 / 59 | |
| 0.20.0 | 0 / 59 | |
| 0.19.2 | 0 / 60 | |
| 0.19.1 | 0 / 60 | |
| 0.19.0 | 0 / 60 | |
| 0.18.1 | 0 / 60 | |
| 0.18.0 | 0 / 59 | |
| 0.17.6 | 0 / 55 | |
| 0.17.5 | 0 / 55 | |
| 0.17.4 | 0 / 55 | |
| 0.17.3 | 0 / 55 | |
| 0.17.2 | 0 / 54 | |
| 0.17.1 | 0 / 54 | |
| 0.17.0 | 0 / 54 | |
| 0.16.7 | 0 / 54 | |
| 0.16.6 | 0 / 54 | |
| 0.16.5 | 0 / 54 | |
| 0.16.4 | 0 / 54 | |
| 0.16.3 | 0 / 54 | |
| 0.16.2 | 0 / 54 | |
| 0.16.1 | 0 / 54 | |
| 0.16.0 | 0 / 54 | |
| 0.15.7 | 0 / 54 | |
| 0.15.6 | 0 / 54 | |
| 0.15.5 | 0 / 54 | |
| 0.15.4 | 0 / 54 | |
| 0.15.3 | 0 / 54 | |
| 0.15.1 | 0 / 54 | |
| 0.15.0 | 0 / 54 | |
| 0.14.0 | 0 / 55 | |
| 0.13.0 | 0 / 55 | |
| 0.12.0 | 0 / 55 | |
| 0.11.0 | 0 / 55 | |
| 0.10.0 | 0 / 55 | |
| 0.9.1 | 0 / 55 | |
| 0.9.0 | 0 / 55 | |
| 0.8.4 | 0 / 55 | |
| 0.8.3 | 0 / 55 | |
| 0.8.2 | 0 / 51 | |
| 0.8.1 | 0 / 51 | |
| 0.8.0 | 0 / 51 | |
| 0.7.1 | 0 / 51 | |
| 0.7.0 | 0 / 51 | |
| 0.6.1 | 0 / 51 | |
| 0.6.0 | 0 / 51 | |
| 0.5.0 | 0 / 51 | |
| 0.4.5 | 0 / 51 | |
| 0.4.4 | 0 / 51 | |
| 0.4.3 | 0 / 51 | |
| 0.4.2 | 0 / 51 | |
| 0.4.1 | 0 / 51 | |
| 0.4.0 | 0 / 49 | |
| 0.3.0 | 0 / 49 | |
| 0.2.4 | 1 / 49 | |
| 0.2.3 | 1 / 49 | |
| 0.2.2 | 1 / 48 | |
| 0.2.1 | 1 / 48 | |
| 0.2.0 | 1 / 48 | |
| 0.1.12 | 1 / 46 | |
| 0.1.11 | 1 / 46 | |
| 0.1.10 | 1 / 47 | |
| 0.1.9 | 1 / 47 | |
| 0.1.8 | 1 / 45 | |
| 0.1.7 | 1 / 46 | |
| 0.1.6 | 1 / 46 | |
| 0.1.5 | 1 / 46 | |
| 0.1.4 | 1 / 46 | |
| 0.1.3 | 1 / 46 | |
| 0.1.2 | 1 / 46 | |
| 0.1.1 | 1 / 46 | |
| 0.1.0 | 1 / 46 | |
| 0.0.1 | 1 / 46 | |
| 0.0.0 | 0 / 4 |
v0.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.