Trust Assessment
bird-dm received a trust score of 91/100, placing it in the Trusted category. This skill has passed all critical security checks and demonstrates strong security practices.
SkillShield's automated analysis identified 2 findings: 0 critical, 0 high, 1 medium, and 1 low severity. Key findings include Unpinned npm dependency version, Unpinned dependencies in package.json.
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 13, 2026 (commit 13146e6a). 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 | Unpinned npm dependency version Dependency '@steipete/bird' is not pinned to an exact version ('^0.8.0'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/tolibear/bird-dms/package.json | |
| LOW | Unpinned dependencies in package.json The `package.json` file specifies dependencies using caret (`^`) version ranges (e.g., `^0.8.0`, `^14.0.0`). While `package-lock.json` pins exact versions for reproducible builds, relying on caret ranges in `package.json` can lead to automatic installation of newer minor or patch versions. These updates, while generally safe, could theoretically introduce breaking changes or security vulnerabilities if a malicious update were to occur in an upstream package and the `package-lock.json` was not present or updated. Consider pinning exact versions for all dependencies in `package.json` (e.g., `1.2.3` instead of `^1.2.3`) to ensure maximum reproducibility and prevent unexpected updates. Regularly audit and update dependencies. | LLM | package.json:19 |
Scan History
Embed Code
[](https://skillshield.io/report/282502cec3053097)
Powered by SkillShield