T08 · Insecure Dependencies
- Location
references/webpush.md:6- Finding
Unpinned Third-Party npm Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent Web Push reference skill, but users should handle push credentials and subscription data carefully.
Install with normal npm supply-chain care, preferably as a pinned local project dependency rather than a global unpinned CLI. Treat VAPID private keys, GCM keys, and push subscription endpoint/key material as sensitive, avoid pasting real secrets into command-line arguments, and disclose and protect backend storage of user push subscriptions.
references/webpush.md:6Unpinned Third-Party npm Dependency Installation
SKILL.md:108Sensitive Push Credentials Passed Through Command-Line Arguments
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# web-push Complete API Reference
## Installation & Configuration
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# web-push Complete API Reference
## Installation & Configuration
The client-side example instructs sending subscription.toJSON() to /api/subscribe, which includes endpoint and key material associated with the user's push subscription. In this markdown file, there is no accompanying warning that subscription details are being transmitted to a backend or that they should be handled as user-associated data.