api-conventions — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited api-conventions (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 1 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
These are the API design standards for our project. Apply these conventions whenever working with API endpoints.
/users, /orders, /products/order-items, /user-profiles/users/{id}/orders/orders?status=active&limit=20All API responses must follow this structure:
{
"data": {},
"error": null,
"meta": {
"page": 1,
"limit": 20,
"total": 100
}
}data: 成功时返回的业务数据error: 错误时返回错误对象 { code, message, details }，成功时为 nullmeta: 分页和元信息，列表接口必须返回@public annotationAuthorization: Bearer <jwt-token>/api/v1/users~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.