Tmp.E4hYN1vheH
v0.4.0Bot 身份认证标准 — 为 AI Agent 和机器人签发加密身份证书,让网站信任你的 bot。 遵循 RFC 9421 HTTP Message Signatures 国际标准,与 Cloudflare Web Bot Auth 生态兼容。 内置 Ed25519 签名注册中心、JWKS 公钥目录、nonce...
⭐ 0· 18·0 current·0 all-time
byCosmos Fang@cosmofang
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
The SKILL.md describes a bot identity/registry system (Ed25519 keys, JWKS, registry, CLI, SDK, extension) and the instructions (git clone, npm install, run registry, generate keys) match that purpose. However, the top-level registry metadata indicated 'no required binaries/env vars' while SKILL.md explicitly lists Node.js >=18 and npm as required—this metadata mismatch should be corrected or confirmed.
Instruction Scope
Instructions focus on catalogued capabilities: running a local registry, key generation, registration, signing, and integrating the SDK/extension. They do not instruct reading unrelated system secrets. Two operational notes: (1) the browser extension will inject headers — confirm how/where signing keys are stored when using the extension (browser-stored private keys can leak if not carefully implemented); (2) some deployment steps reference environment variables (PORT, VITE_REGISTRY_URL, optional RIC_ADMIN_KEY for Render) — these are expected for deployment but should be treated as sensitive.
Install Mechanism
The skill is instruction-only (no install spec) which is low risk: it tells users to git clone the public GitHub repo and run npm install/build. That is standard for a Node project. Confirm you are cloning the official upstream repository and inspect the repo contents (packages) before running npm install. No arbitrary archive downloads or obscure URLs are requested.
Credentials
The skill does not declare any required secrets and only references plausible deployment secrets (optional RIC_ADMIN_KEY for an admin role, VITE_REGISTRY_URL). This is proportionate to running a registry/website. The SKILL.md asserts it does not read or transmit third-party API tokens; you should verify that in the upstream code before deploying.
Persistence & Privilege
The project writes its own local files (SQLite DB under packages/registry/data/registry.db, generated key files at user-specified paths, build outputs). It does not request elevated privileges, does not set always:true, and claims not to modify system config or create cron jobs. These behaviors are appropriate for a local registry/CLI tool.
Assessment
This skill appears to be what it says — a bot identity standard and local registry — but take these precautions before installing or deploying: 1) Metadata mismatch: SKILL.md requires Node.js and npm; confirm the environment has Node >=18 before proceeding. 2) Review upstream code: the skill instructs cloning and running npm install; inspect the repository (packages/registry, cli, sdk, extension) for any unexpected behavior before running. 3) Protect private keys: never upload your bot private key to untrusted services; follow the project's guidance that private keys remain local. 4) Browser extension caution: extensions that auto-sign or inject headers may need access to keys — review extension code and permissions; avoid loading unsigned/unreviewed extensions into a production browser. 5) Deployment secrets: if you deploy a registry, store RIC_ADMIN_KEY and other secrets in a secure secrets store (Render/Netlify/Environment) and rotate keys if exposed. 6) Sandbox first: run the registry locally in an isolated environment, confirm audit-logging behavior, and validate what data is published to any public audit log. If you want more confidence, provide the upstream repository URL or a copy of the registry/cli source files for a deeper code-level review.Like a lobster shell, security has layers — review code before you run it.
latestvk97cd7pa38tpwjbe8dwc5vw0m9851e2x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
