Trust Assessment
api-design-principles received a trust score of 63/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 3 findings: 0 critical, 2 high, 1 medium, and 0 low severity. Key findings include Unsafe deserialization / dynamic eval, Broad CORS Policy (Wildcard Origin), Wildcard Trusted Host Configuration.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on June 1, 2026 (commit 0818067b). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Unsafe deserialization / dynamic eval Decryption followed by code execution Remove obfuscated code execution patterns. Legitimate code does not need base64-encoded payloads executed via eval, encrypted-then-executed blobs, or dynamic attribute resolution to call system functions. | Manifest | plugins/backend-development/skills/api-design-principles/assets/rest-api-template.py:3 | |
| HIGH | Broad CORS Policy (Wildcard Origin) The FastAPI application is configured with `CORSMiddleware` allowing all origins (`allow_origins=["*"]`). While this is noted as a TODO for production, in a deployed scenario, this configuration allows any website to make cross-origin requests to the API. This can lead to various attacks, including CSRF (if `allow_credentials` were true and not properly handled) or information leakage if the API serves sensitive data without proper authentication/authorization. Restrict `allow_origins` to a specific list of trusted domains in production environments. For development, consider using a more granular approach or ensuring the API does not handle sensitive data without authentication. | Static | assets/rest-api-template.py:26 | |
| MEDIUM | Wildcard Trusted Host Configuration The `TrustedHostMiddleware` is configured with `allowed_hosts=["*"]`. This setting, while explicitly marked as a TODO for production, allows the API to respond to requests from any host header. In a production environment, this makes the application vulnerable to HTTP Host Header attacks, where an attacker can manipulate the Host header to point to a malicious domain, potentially leading to cache poisoning, password reset poisoning, or other exploits. In production, configure `allowed_hosts` with a specific list of trusted domain names that the API is expected to serve. For development, ensure this template is not deployed as-is to a public-facing environment. | Static | assets/rest-api-template.py:20 |
Scan History
Embed Code
[](https://skillshield.io/report/9970de573e16f6f2)
Powered by SkillShield