@volar/test-utils
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Test utility package legitimately spawns language server processes; child_process use is expected and benign here. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 2.4.28 | 4 / 0 | |
| 2.4.27 | 4 / 0 | |
| 2.4.26 | 4 / 0 | |
| 2.4.25 | 4 / 0 | |
| 2.4.24 | 4 / 1 | |
| 2.4.23 | 4 / 1 | |
| 2.4.22 | 4 / 1 | |
| 2.4.21 | 4 / 1 | |
| 2.4.20 | 4 / 1 | |
| 2.4.19 | 4 / 1 | |
| 2.4.18 | 4 / 1 | |
| 2.4.17 | 4 / 1 | |
| 2.4.16 | 4 / 1 | |
| 2.4.15 | 4 / 1 | |
| 2.4.14 | 4 / 1 | |
| 2.4.13 | 4 / 1 | |
| 2.4.12 | 4 / 1 | |
| 2.4.11 | 4 / 1 | |
| 2.4.10 | 4 / 1 | |
| 2.4.9 | 4 / 1 | |
| 2.4.8 | 4 / 1 | |
| 2.4.7 | 4 / 1 | |
| 2.4.6 | 4 / 1 | |
| 2.4.5 | 4 / 1 | |
| 2.4.4 | 4 / 1 | |
| 2.4.3 | 4 / 1 | |
| 2.4.2 | 4 / 1 | |
| 2.4.1 | 4 / 1 | |
| 2.4.0 | 4 / 1 | |
| 2.3.4 | 4 / 1 | |
| 2.3.3 | 4 / 1 | |
| 2.3.2 | 4 / 1 | |
| 2.3.1 | 4 / 1 | |
| 2.3.0 | 4 / 1 | |
| 2.2.5 | 4 / 1 | |
| 2.2.4 | 4 / 1 | |
| 2.2.3 | 4 / 1 | |
| 2.2.2 | 4 / 1 | |
| 2.2.1 | 4 / 1 |
v2.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.