hono

v1.0.0

Hono web framework skill for building APIs across all JS runtimes (Cloudflare Workers, Deno, Bun, Node.js, etc.). Covers routing, middleware, JSX, RPC client...

0· 49·0 current·0 all-time
by岳晓亮@yuexiaoliang
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the included documentation: routing, middleware, JSX, RPC client, validators, and context examples. The skill does not request unrelated binaries, credentials, or config paths.
Instruction Scope
SKILL.md and reference files are documentation and code examples for using Hono. They reference runtime constructs (c.env, crypto, fetch, service bindings, JWT secrets) as expected for framework examples — but they do not instruct the agent to read host files, exfiltrate data, or access environment variables beyond illustrative usage.
Install Mechanism
No install spec or downloads are present (instruction-only). Nothing will be written to disk or executed by an installer when the skill is installed.
Credentials
The skill declares no required environment variables or credentials. Examples show using secrets (JWT signingKey, API_KEY) but these are illustrative and not requested by the skill itself.
Persistence & Privilege
always is false; the skill is user-invocable and can be called autonomously (platform default) but it does not request elevated persistence or modify other skills/configuration.
Assessment
This bundle is documentation/examples for the Hono framework and appears coherent and low-risk as provided. Before using it in a project: install Hono packages from the official source (npm/github) and verify package integrity; replace example secrets (signingKey, API_KEY) with appropriately scoped credentials; and review any third‑party middleware you add (e.g., jwt, proxy, fetch calls) to ensure they don't send sensitive data to unknown endpoints.

Like a lobster shell, security has layers — review code before you run it.

latestvk9773amerqqxnhy5dy99r65eqs84rt46

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments