@visactor/vgrammar-core
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@visactor/vdataset | AI (dependencies): Same-org sibling dep in VisActor monorepo; consistent across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): VisActor monorepo package; README link dump and missing repo URL are cosmetic issues, not spam indicators. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.16.17 | 8 / 14 | |
| 0.16.16 | 8 / 14 | |
| 0.16.15 | 8 / 14 | |
| 0.16.14 | 8 / 14 | |
| 0.16.13 | 8 / 14 | |
| 0.16.12 | 8 / 14 | |
| 0.16.11 | 8 / 14 | |
| 0.16.10 | 8 / 14 | |
| 0.16.9 | 8 / 14 | |
| 0.16.8 | 8 / 14 | |
| 0.16.7 | 8 / 14 |
v0.16.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.