@visactor/vgrammar-coordinate
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): Transition to GitHub Actions CI publishing is legitimate for VisActor org; backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-automated publish with SLSA attestation; no malicious indicators in diff. | ai | |
| phantom-deps | phantom-dep:@visactor/vgrammar-util | AI (phantom-deps): Same-org dependency declared in package.json; likely used transitively or in build artifacts rather than direct imports. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.16.17 | 2 / 14 | |
| 0.16.16 | 2 / 14 | |
| 0.16.15 | 2 / 14 | |
| 0.16.14 | 2 / 14 | |
| 0.16.13 | 2 / 14 | |
| 0.16.12 | 2 / 14 | |
| 0.16.11 | 2 / 14 | |
| 0.16.10 | 2 / 14 | |
| 0.16.9 | 2 / 14 | |
| 0.16.8 | 2 / 14 | |
| 0.16.7 | 2 / 14 | |
| 0.16.6 | 2 / 14 | |
| 0.16.5 | 2 / 14 | |
| 0.16.4 | 2 / 14 | |
| 0.16.3 | 2 / 14 | |
| 0.16.2 | 2 / 14 | |
| 0.16.1 | 2 / 14 | |
| 0.16.0 | 2 / 14 | |
| 0.15.7 | 2 / 14 | |
| 0.15.6 | 2 / 14 | |
| 0.15.5 | 2 / 14 | |
| 0.15.4 | 2 / 14 | |
| 0.15.3 | 2 / 14 | |
| 0.15.2 | 2 / 14 | |
| 0.15.1 | 2 / 14 | |
| 0.15.0 | 2 / 14 | |
| 0.14.23 | 2 / 14 | |
| 0.14.22 | 2 / 14 | |
| 0.14.21 | 2 / 14 | |
| 0.14.20 | 2 / 14 | |
| 0.14.19 | 2 / 14 | |
| 0.14.18 | 2 / 14 | |
| 0.14.17 | 2 / 14 | |
| 0.14.16 | 2 / 14 | |
| 0.14.15 | 2 / 14 | |
| 0.14.14 | 2 / 14 | |
| 0.14.13 | 2 / 14 | |
| 0.14.12 | 2 / 14 | |
| 0.14.11 | 2 / 14 | |
| 0.14.10 | 2 / 14 | |
| 0.14.9 | 2 / 14 | |
| 0.14.8 | 2 / 14 | |
| 0.14.7 | 2 / 14 | |
| 0.14.6 | 2 / 14 | |
| 0.14.5 | 2 / 14 | |
| 0.14.4 | 2 / 14 | |
| 0.14.3 | 2 / 14 | |
| 0.14.2 | 2 / 14 | |
| 0.14.1 | 2 / 14 | |
| 0.14.0 | 2 / 14 | |
| 0.13.22 | 2 / 14 | |
| 0.13.21 | 2 / 14 | |
| 0.13.20 | 2 / 14 | |
| 0.13.19 | 2 / 14 | |
| 0.13.18 | 2 / 14 | |
| 0.13.17 | 2 / 14 | |
| 0.13.16 | 2 / 14 | |
| 0.13.15 | 2 / 14 | |
| 0.13.14 | 2 / 14 | |
| 0.13.13 | 2 / 14 | |
| 0.13.12 | 2 / 14 | |
| 0.13.11 | 2 / 14 | |
| 0.13.10 | 2 / 14 | |
| 0.13.9 | 2 / 14 | |
| 0.13.8 | 2 / 14 | |
| 0.13.7 | 2 / 14 | |
| 0.13.6 | 2 / 14 | |
| 0.13.5 | 2 / 14 | |
| 0.13.4 | 2 / 14 | |
| 0.13.3 | 2 / 14 | |
| 0.13.2 | 2 / 14 | |
| 0.13.1 | 2 / 14 | |
| 0.12.12 | 2 / 14 |
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
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 (xile611) on 2025-04-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.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.