Security Audit
azure-storage-file-share-ts
github.com/sickn33/antigravity-awesome-skillsTrust Assessment
azure-storage-file-share-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 1 finding: 0 critical, 0 high, 1 medium, and 0 low severity. Key findings include Unpinned npm dependencies.
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 Findings1
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Unpinned npm dependencies The `npm install` command specifies major versions (`@azure/storage-file-share`, `@azure/identity`) but does not pin to exact versions. This can lead to non-deterministic builds and potentially pull in vulnerable or malicious package updates if a new version within the specified range is compromised. Without exact version pinning or a lock file, the integrity of the dependency chain cannot be guaranteed. Pin dependencies to exact versions (e.g., `npm install @azure/storage-file-share@12.17.0 @azure/identity@4.0.0`) or ensure a lock file (`package-lock.json` or `yarn.lock`) is used and committed to guarantee deterministic builds and prevent unexpected dependency changes. | LLM | SKILL.md:13 |
Scan History
Embed Code
[](https://skillshield.io/report/ae7277deb5addb67)
Powered by SkillShield