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 100 of 194)
| Version | Deps | Published |
|---|---|---|
| 0.50.0 | 0 / 94 | |
| 0.49.3 | 0 / 86 | |
| 0.49.2 | 0 / 86 | |
| 0.49.1 | 0 / 87 | |
| 0.49.0 | 0 / 87 | |
| 0.48.8 | 0 / 87 | |
| 0.48.7 | 0 / 87 | |
| 0.48.6 | 0 / 84 | |
| 0.48.5 | 0 / 85 | |
| 0.48.4 | 0 / 85 | |
| 0.48.3 | 0 / 83 | |
| 0.48.2 | 0 / 83 | |
| 0.48.1 | 0 / 83 | |
| 0.48.0 | 0 / 83 | |
| 0.47.2 | 0 / 83 | |
| 0.47.1 | 0 / 83 | |
| 0.47.0 | 0 / 83 | |
| 0.46.7 | 0 / 83 | |
| 0.46.6 | 0 / 83 | |
| 0.46.5 | 0 / 83 | |
| 0.46.4 | 0 / 82 | |
| 0.46.3 | 0 / 82 | |
| 0.46.2 | 0 / 82 | |
| 0.46.1 | 0 / 82 | |
| 0.46.0 | 0 / 82 | |
| 0.45.3 | 0 / 82 | |
| 0.45.2 | 0 / 82 | |
| 0.45.1 | 0 / 82 | |
| 0.45.0 | 0 / 82 | |
| 0.44.3 | 0 / 82 | |
| 0.44.2 | 0 / 82 | |
| 0.44.1 | 0 / 81 | |
| 0.44.0 | 0 / 80 | |
| 0.43.6 | 0 / 80 | |
| 0.43.5 | 0 / 80 | |
| 0.43.4 | 0 / 81 | |
| 0.43.3 | 0 / 82 | |
| 0.43.2 | 0 / 82 | |
| 0.43.1 | 0 / 82 | |
| 0.43.0 | 0 / 82 | |
| 0.42.4 | 0 / 82 | |
| 0.42.3 | 0 / 82 | |
| 0.42.2 | 0 / 82 | |
| 0.42.1 | 0 / 82 | |
| 0.42.0 | 0 / 82 | |
| 0.41.5 | 0 / 89 | |
| 0.41.4 | 0 / 89 | |
| 0.41.3 | 0 / 89 | |
| 0.41.2 | 0 / 92 | |
| 0.41.1 | 0 / 92 | |
| 0.41.0 | 0 / 92 | |
| 0.40.4 | 0 / 92 | |
| 0.40.3 | 0 / 92 | |
| 0.40.2 | 0 / 92 | |
| 0.40.1 | 0 / 92 | |
| 0.40.0 | 0 / 92 | |
| 0.39.3 | 0 / 92 | |
| 0.39.2 | 0 / 92 | |
| 0.39.1 | 0 / 92 | |
| 0.39.0 | 0 / 92 | |
| 0.38.5 | 0 / 92 | |
| 0.38.4 | 0 / 92 | |
| 0.38.3 | 0 / 92 | |
| 0.38.2 | 0 / 92 | |
| 0.38.1 | 0 / 92 | |
| 0.38.0 | 0 / 92 | |
| 0.37.4 | 0 / 92 | |
| 0.37.3 | 0 / 92 | |
| 0.37.2 | 0 / 92 | |
| 0.37.1 | 0 / 92 | |
| 0.37.0 | 0 / 92 | |
| 0.36.3 | 0 / 92 | |
| 0.36.2 | 0 / 92 | |
| 0.36.1 | 0 / 92 | |
| 0.36.0 | 0 / 92 | |
| 0.35.1 | 0 / 94 | |
| 0.35.0 | 0 / 94 | |
| 0.34.2 | 0 / 93 | |
| 0.34.1 | 0 / 93 | |
| 0.34.0 | 0 / 93 | |
| 0.33.7 | 0 / 93 | |
| 0.33.6 | 0 / 93 | |
| 0.33.5 | 0 / 93 | |
| 0.33.4 | 0 / 93 | |
| 0.33.3 | 0 / 92 | |
| 0.33.2 | 0 / 89 | |
| 0.33.1 | 0 / 88 | |
| 0.33.0 | 0 / 88 | |
| 0.32.0 | 0 / 88 | |
| 0.31.0 | 0 / 87 | |
| 0.30.5 | 0 / 80 | |
| 0.30.4 | 0 / 80 | |
| 0.30.3 | 0 / 80 | |
| 0.30.2 | 0 / 79 | |
| 0.30.1 | 0 / 79 | |
| 0.30.0 | 0 / 79 | |
| 0.29.2 | 0 / 77 | |
| 0.29.1 | 0 / 73 | |
| 0.29.0 | 0 / 73 | |
| 0.28.0 | 0 / 72 |
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.40.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.40.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.40.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.40.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.39.3
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.39.2
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.39.1
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.39.0
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.38.5
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.38.4
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.38.3
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.38.2
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.38.1
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.38.0
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.37.4
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.37.3
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.37.2
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.37.1
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.37.0
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.36.3
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.36.2
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.36.1
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.36.0
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.35.1
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.35.0
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.34.2
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.34.1
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.34.0
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.33.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.33.6
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.33.5
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.33.4
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.33.3
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.33.2
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.33.1
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.33.0
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.32.0
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.31.0
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.30.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.