volar-service-emmet
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:@emmetio/css-parser | AI (dependencies): @emmetio/css-parser is a canonical Emmet ecosystem package; its use is expected and appropriate for a volar-service-emmet integration package. | ai | |
| dependencies | unvetted-dep:@emmetio/html-matcher | AI (dependencies): @emmetio/html-matcher is a canonical Emmet ecosystem package; its use is expected and appropriate for a volar-service-emmet integration package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.71 | 4 / 1 | |
| 0.0.70 | 4 / 1 | |
| 0.0.69 | 4 / 1 | |
| 0.0.68 | 4 / 1 | |
| 0.0.67 | 4 / 1 | |
| 0.0.66 | 4 / 1 | |
| 0.0.65 | 4 / 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.70
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.