@voltagent/server-hono
Hono server implementation for VoltAgent
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has strong track record (25 approved, 0 rejected); no suspicious changes in this release. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| dependencies | unvetted-dep:@voltagent/core | AI (dependencies): Same-org monorepo dependency; stable pattern across all @voltagent/* packages. | ai | |
| phantom-deps | phantom-dep:@voltagent/mcp-server | AI (phantom-deps): Same-org monorepo package; declared as a dependency, phantom-dep heuristic is a false positive here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.0.13 | 11 / 2 | |
| 2.0.12 | 11 / 2 | |
| 2.0.11 | 11 / 2 | |
| 2.0.10 | 11 / 2 | |
| 2.0.9 | 11 / 2 | |
| 2.0.8 | 11 / 2 | |
| 2.0.7 | 11 / 2 | |
| 2.0.6 | 11 / 2 | |
| 2.0.5 | 11 / 2 | |
| 2.0.4 | 11 / 2 | |
| 2.0.3 | 11 / 2 | |
| 2.0.2 | 10 / 2 | |
| 2.0.1 | 10 / 2 | |
| 1.2.11 | 10 / 2 | |
| 1.2.10 | 10 / 2 | |
| 1.2.9 | 10 / 2 | |
| 1.2.8 | 10 / 2 | |
| 1.2.7 | 10 / 2 | |
| 1.2.6 | 10 / 2 | |
| 1.2.5 | 10 / 2 | |
| 1.2.4 | 10 / 2 | |
| 1.2.3 | 10 / 2 |
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.