← Home

@visactor/vgrammar-venn

npm Repository Homepage

Venn layout transform for VGrammar

11
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

liufangfangvisactorownerxuanhunzamhownchensiji.0517youngwindspurpose233ssfxzlixuefei.1313ray_sunxiaoluohesimaqxile611da730zhouxinyu66888zexian_chen

Keywords

vennvisualizationVGrammarstorytellingVisActor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; consistent with org-level CI migration. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI-attested publish from official VisActor repo; no malicious indicators. ai
phantom-deps phantom-dep:@visactor/vrender-kits AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on build-time vs runtime split, not a real concern. ai
phantom-deps phantom-dep:@visactor/vgrammar-util AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
0.16.17 5 / 14
0.16.16 5 / 14
0.16.15 5 / 14
0.16.14 5 / 14
0.16.13 5 / 14
0.16.12 5 / 14
0.16.11 5 / 14
0.16.10 5 / 14
0.16.9 5 / 14
0.16.8 5 / 14
0.16.7 5 / 14

v0.16.17

2 findings
HIGH Publisher changed: lixuefei.1313 → GitHub Actions (on 2026-03-27) provenance

This version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.