@visactor/vtable-plugins
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 | 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 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 1.26.4 | 6 / 50 | |
| 1.26.1 | 6 / 50 | |
| 1.26.0 | 6 / 50 | |
| 1.25.0 | 6 / 50 | |
| 1.24.0 | 6 / 50 | |
| 1.23.3 | 6 / 50 | |
| 1.23.2 | 6 / 50 | |
| 1.23.1 | 6 / 50 | |
| 1.23.0 | 6 / 50 | |
| 1.22.12 | 6 / 50 | |
| 1.22.11 | 6 / 50 | |
| 1.22.10 | 6 / 50 | |
| 1.22.9 | 6 / 50 | |
| 1.22.8 | 6 / 50 | |
| 1.22.7 | 6 / 50 | |
| 1.22.6 | 6 / 50 | |
| 1.22.5 | 6 / 50 | |
| 1.22.4 | 6 / 50 | |
| 1.22.3 | 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 | |
| 1.18.2 | 1 / 46 | |
| 1.18.1 | 1 / 46 | |
| 1.18.0 | 1 / 46 | |
| 1.17.7 | 1 / 46 | |
| 1.17.6 | 1 / 46 | |
| 1.17.5 | 1 / 46 | |
| 1.17.4 | 1 / 46 | |
| 1.17.3 | 1 / 46 | |
| 1.17.2 | 1 / 46 | |
| 1.17.1 | 1 / 46 | |
| 1.17.0 | 1 / 46 | |
| 1.16.2 | 1 / 46 | |
| 1.16.1 | 1 / 46 | |
| 1.16.0 | 1 / 46 | |
| 1.15.2 | 1 / 46 | |
| 1.15.1 | 1 / 46 | |
| 1.15.0 | 1 / 46 | |
| 1.14.3 | 1 / 46 | |
| 1.14.2 | 1 / 46 | |
| 1.14.1 | 1 / 46 | |
| 1.14.0 | 1 / 46 | |
| 1.13.2 | 1 / 46 | |
| 1.13.1 | 1 / 46 | |
| 1.13.0 | 1 / 46 | |
| 1.12.0 | 1 / 46 | |
| 1.11.6 | 1 / 45 | |
| 1.11.5 | 1 / 45 | |
| 1.11.1 | 1 / 44 |
v1.26.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (liufangfang) on 2026-07-06, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.25.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (liufangfang) than the most recent previously approved version (chensiji.0517) on 2026-03-25, but liufangfang is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (liufangfang) than the most recent previously approved version (chensiji.0517) on 2026-03-18, but liufangfang is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chensiji.0517) than the most recent previously approved version (liufangfang) on 2025-12-28, but chensiji.0517 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.22.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chensiji.0517) than the most recent previously approved version (liufangfang) on 2025-12-17, but chensiji.0517 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.22.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (liufangfang) than the most recent previously approved version (ray_sun) on 2024-11-29, but liufangfang is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.