@visactor/vtable
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): liufangfang is a known VisActor org maintainer with 114 approved packages and no rejections; transition appears legitimate. | ai | |
| dependencies | unvetted-dep:@visactor/vdataset | AI (dependencies): Same VisActor org dependency; stable sibling package used across the vtable ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo package; provenance absence is consistent across all @visactor/* releases. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.26.5 | 13 / 53 | |
| 1.26.4 | 12 / 53 | |
| 1.26.3 | 12 / 53 | |
| 1.26.2 | 12 / 53 | |
| 1.26.1 | 12 / 53 | |
| 1.26.0 | 12 / 53 | |
| 1.25.0 | 12 / 53 | |
| 1.24.0 | 12 / 53 | |
| 1.23.3 | 12 / 53 | |
| 1.23.2 | 12 / 53 | |
| 1.23.1 | 12 / 53 | |
| 1.23.0 | 12 / 53 | |
| 1.22.12 | 12 / 53 | |
| 1.22.11 | 12 / 53 | |
| 1.22.10 | 12 / 53 | |
| 1.22.9 | 12 / 53 | |
| 1.22.8 | 12 / 53 | |
| 1.22.7 | 12 / 53 | |
| 1.22.6 | 12 / 53 | |
| 1.22.5 | 12 / 53 | |
| 1.22.4 | 12 / 53 | |
| 1.22.3 | 12 / 53 | |
| 1.18.12 | 11 / 51 | |
| 1.18.11 | 11 / 51 |
v1.26.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.26.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.26.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.0
2 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.9
2 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.