volar-service-yaml
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yaml-language-server | AI (phantom-deps): volar-service-yaml wraps yaml-language-server; likely used indirectly via requires/dynamic import in built output. | ai | |
| dependencies | unvetted-dep:yaml-language-server | AI (dependencies): yaml-language-server is the core dependency this package is explicitly designed to integrate; its inclusion is expected and intentional across all versions. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.0.71 | 2 / 1 | |
| 0.0.70 | 2 / 1 | |
| 0.0.69 | 2 / 1 | |
| 0.0.68 | 2 / 1 | |
| 0.0.67 | 2 / 1 | |
| 0.0.66 | 2 / 1 | |
| 0.0.65 | 2 / 1 | |
| 0.0.64 | 2 / 1 | |
| 0.0.63 | 2 / 1 | |
| 0.0.62 | 2 / 1 | |
| 0.0.61 | 2 / 1 | |
| 0.0.60 | 2 / 1 | |
| 0.0.59 | 2 / 1 | |
| 0.0.58 | 2 / 1 | |
| 0.0.57 | 2 / 1 | |
| 0.0.56 | 2 / 1 | |
| 0.0.55 | 2 / 1 | |
| 0.0.54 | 2 / 1 | |
| 0.0.53 | 2 / 1 | |
| 0.0.52 | 2 / 1 | |
| 0.0.51 | 2 / 1 | |
| 0.0.50 | 2 / 1 | |
| 0.0.49 | 2 / 1 | |
| 0.0.48 | 2 / 1 | |
| 0.0.47 | 2 / 1 | |
| 0.0.46 | 2 / 1 | |
| 0.0.45 | 2 / 1 | |
| 0.0.44 | 2 / 1 | |
| 0.0.43 | 2 / 1 | |
| 0.0.42 | 2 / 1 | |
| 0.0.41 | 2 / 1 | |
| 0.0.40 | 2 / 1 | |
| 0.0.39 | 2 / 1 | |
| 0.0.38 | 2 / 1 | |
| 0.0.37 | 2 / 1 | |
| 0.0.36 | 2 / 1 | |
| 0.0.35 | 2 / 1 | |
| 0.0.34 | 2 / 1 | |
| 0.0.33 | 2 / 1 | |
| 0.0.32 | 2 / 1 | |
| 0.0.31 | 2 / 1 | |
| 0.0.30 | 1 / 1 | |
| 0.0.29 | 1 / 1 | |
| 0.0.28 | 1 / 1 | |
| 0.0.27 | 1 / 1 | |
| 0.0.26 | 1 / 1 | |
| 0.0.25 | 1 / 1 | |
| 0.0.24 | 1 / 1 | |
| 0.0.23 | 1 / 1 | |
| 0.0.22 | 1 / 1 | |
| 0.0.21 | 1 / 1 |
v0.0.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.