T08 · Insecure Dependencies
- Location
skill.md:61- Finding
Unpinned External npm Package Installation in Skill Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent with its legal and payment purpose, but it promotes autonomous contract signing and escrow/payment actions with weak safeguards and relies on unverifiable mutable installs.
Review carefully before installing. Use only a sandbox or staging environment first, pin and verify the npm package or Git commit, disable install scripts during inspection when possible, and require explicit human approval for signing contracts, depositing funds, releasing escrow, refunds, and dispute rulings.
skill.md:61Unpinned External npm Package Installation in Skill Instructions
readme.md:53Mutable npm and Git Dependency Installation Instructions
The README explicitly demonstrates escrow deposit and release operations and promotes automated contract execution, but it does not warn that these actions can move funds or trigger irreversible legal/financial state changes. In an agent-oriented commerce framework, readers may treat example commands as safe defaults, increasing the risk of accidental payment release, unauthorized execution flows, or misuse in testing against real accounts.
The skill explicitly promotes autonomous negotiation, signing, execution, and enforcement of commercial agreements, along with escrow and payment handling, but does not prominently warn that these are legally and financially consequential actions. In an agent setting, this can normalize high-risk automation and lead users to deploy workflows that commit funds or enter binding agreements without sufficient human review or transactional safeguards.
The quick-start and CLI examples show how to register agents, create contracts with escrow, and enable milestone-based payment flows without any prominent caution that the operations may affect real money or create irreversible obligations. Because examples are often copied directly into production-like environments, this increases the likelihood of unsafe deployment by users who assume the workflow is low risk or purely demonstrative.
No suspicious patterns detected.