@visactor/vtable-export
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/vtable-export.js | AI (source-diff): Long strings are minified exceljs bundle content, not obfuscated payloads; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/vtable-export.min.js | AI (source-diff): Minified dist file; long strings are standard minification output for bundled dependencies. | ai | |
| phantom-deps | phantom-dep:@types/file-saver | AI (phantom-deps): @types/file-saver is a type declaration package listed as a runtime dep; phantom-dep false positive for this package. | ai |
Versions (showing 20 of 120)
| Version | Deps | Published |
|---|---|---|
| 1.5.4 | 5 / 44 | |
| 1.5.3 | 5 / 44 | |
| 1.5.2 | 5 / 44 | |
| 1.5.1 | 5 / 44 | |
| 1.5.0 | 5 / 44 | |
| 1.4.2 | 5 / 44 | |
| 1.4.1 | 5 / 44 | |
| 1.4.0 | 5 / 44 | |
| 1.3.3 | 5 / 44 | |
| 1.3.2 | 5 / 44 | |
| 1.3.1 | 5 / 44 | |
| 1.3.0 | 5 / 44 | |
| 1.2.0 | 5 / 44 | |
| 1.1.2 | 5 / 44 | |
| 1.1.1 | 5 / 44 | |
| 1.1.0 | 5 / 44 | |
| 1.0.3 | 5 / 44 | |
| 1.0.2 | 5 / 44 | |
| 1.0.1 | 5 / 44 | |
| 1.0.0 | 5 / 44 |
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.