@visactor/vtable-plugins
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:cjs/auto-fill/auto-fill-helper.js | AI (source-diff): Minified build output with readable logic; no obfuscation or malicious patterns. | ai | |
| source-diff | obfuscated-file:es/auto-fill/auto-fill-helper.js | AI (source-diff): Minified build output with readable logic; no obfuscation or malicious patterns. | ai | |
| source-diff | encoded-string-file:dist/vtable-plugins.js | AI (source-diff): Long strings are bundled exceljs minified library, consistent with new exceljs dependency. | ai | |
| source-diff | encoded-string-file:dist/vtable-plugins.min.js | AI (source-diff): Long strings are bundled exceljs minified library, consistent with new exceljs dependency. | ai | |
| phantom-deps | phantom-dep:@types/file-saver | AI (phantom-deps): @types packages are type-only and not directly imported at runtime. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.26.1 | 6 / 50 | |
| 1.26.0 | 6 / 50 | |
| 1.23.2 | 6 / 50 | |
| 1.21.1 | 6 / 50 | |
| 1.21.0 | 6 / 50 | |
| 1.20.3 | 6 / 50 | |
| 1.20.2 | 6 / 50 | |
| 1.19.1 | 3 / 48 | |
| 1.19.0 | 3 / 48 | |
| 1.18.12 | 1 / 47 | |
| 1.18.11 | 1 / 47 | |
| 1.18.10 | 1 / 47 | |
| 1.18.9 | 1 / 47 | |
| 1.18.8 | 1 / 47 | |
| 1.18.7 | 1 / 47 | |
| 1.18.6 | 1 / 47 | |
| 1.18.5 | 1 / 47 | |
| 1.18.4 | 1 / 47 | |
| 1.18.3 | 1 / 47 |
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
5 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.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
5 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.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
5 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.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
5 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.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.