@hono/vite-dev-server
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 2 / 8 | |
| 0.25.3 | 2 / 8 | |
| 0.25.2 | 2 / 8 | |
| 0.25.1 | 2 / 12 | |
| 0.25.0 | 2 / 12 | |
| 0.24.1 | 2 / 12 | |
| 0.24.0 | 2 / 12 | |
| 0.23.0 | 2 / 11 | |
| 0.22.0 | 2 / 11 | |
| 0.21.1 | 2 / 11 | |
| 0.21.0 | 2 / 11 | |
| 0.20.1 | 2 / 11 | |
| 0.20.0 | 2 / 11 | |
| 0.19.1 | 2 / 11 |
v0.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.