Security Audit
azure-storage-blob-ts
github.com/sickn33/antigravity-awesome-skillsTrust Assessment
azure-storage-blob-ts received a trust score of 85/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.
SkillShield's automated analysis identified 2 findings: 0 critical, 0 high, 1 medium, and 1 low severity. Key findings include Unpinned dependencies in installation instructions, Example demonstrates generation of overly broad SAS token.
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 February 20, 2026 (commit e36d6fd3). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings2
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Example demonstrates generation of overly broad SAS token The documentation provides an example for generating an Account SAS token with `AccountSASPermissions.parse('rwdlacupi')`, which grants 'all permissions' (read, write, delete, list, add, create, update, process, immutable storage) across all services and resource types. While this is an example, it encourages the creation of highly privileged tokens. If an agent or user were to implement this example directly without narrowing permissions, it could lead to significant security risks if the generated token is compromised or misused. Revise the example to demonstrate the principle of least privilege. Suggest generating SAS tokens with only the minimum necessary permissions for the intended operation. For instance, show an example with read-only access or specific container/blob permissions, and add a warning about the dangers of granting 'all permissions'. | LLM | SKILL.md:260 | |
| LOW | Unpinned dependencies in installation instructions The installation instructions recommend installing `@azure/storage-blob` and `@azure/identity` without specifying a version. This can lead to unexpected behavior or security vulnerabilities if a new major version introduces breaking changes or if a malicious update is published to an unpinned dependency. It's best practice to pin dependencies to specific versions or use caret/tilde ranges for minor/patch updates. Update the installation instructions to recommend pinning dependency versions, e.g., `npm install @azure/storage-blob@^12.0.0 @azure/identity@^3.0.0` or specific versions like `@azure/storage-blob@12.17.0`. | LLM | SKILL.md:10 |
Scan History
Embed Code
[](https://skillshield.io/report/7f31412ad6e588c1)
Powered by SkillShield