Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed traffic-query skill that reads only named API-key environment variables and makes purpose-aligned map API requests, though its docs and dependencies need cleanup.
Install only if you are comfortable giving this Node CLI the listed map/SCATS API keys and allowing outbound requests to map providers. Before production use, fix the missing/incorrect command documentation, document the config command, and update or pin the HTTP dependencies after auditing them.
The documented behavior does not match the detected capabilities: advertised SCATS and incident support may be incomplete, while an undeclared configuration-inspection capability exists. Behavior mismatches are dangerous because they undermine operator trust and can hide functionality that exposes configuration, secrets, or unexpected data flows beyond the user-approved purpose.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
const axios = require('axios');
// Get API keys from environment
const BAIDU_MAP_KEY = process.env.BAIDU_MAP_KEY || '';
const GAODE_MAP_KEY = process.env.GAODE_MAP_KEY || '';
const SCATS_API_KEY = process.env.SCATS_API_KEY || '';
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
async function queryRoad(city, road) {
if (!GAODE_MAP_KEY && !BAIDU_MAP_KEY) {
console.log('Error: Please configure map API key in .env file');
console.log('GAODE_MAP_KEY or BAIDU_MAP_KEY required');
return;
}
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
async function queryRoad(city, road) {
if (!GAODE_MAP_KEY && !BAIDU_MAP_KEY) {
console.log('Error: Please configure map API key in .env file');
console.log('GAODE_MAP_KEY or BAIDU_MAP_KEY required');
return;
}
The lockfile pins axios 1.13.5, and the supplied advisories include high-risk issues such as NO_PROXY normalization bypass leading to SSRF as well as prototype-pollution-related MITM/credential theft scenarios. In a traffic-data skill that makes outbound HTTP requests to external APIs, a vulnerable HTTP client is directly security-relevant because it may allow request routing bypasses, credential leakage, or response tampering depending on how the library is used.
form-data 4.0.5 is reported as vulnerable to CRLF injection via unescaped multipart field names and filenames. If this skill ever constructs multipart requests using attacker-influenced values, an attacker may be able to manipulate request boundaries or inject crafted headers/content, potentially altering requests sent to upstream services.
The package allows resolution to an axios version reported as vulnerable, including SSRF and man-in-the-middle/prototype-pollution-related issues. Because this skill appears to fetch real-time traffic and incident data from remote services, a vulnerable HTTP client can expose requests, credentials, or internal network access paths if the surrounding code uses proxies, attacker-influenced URLs, or unsafe object handling.
The skill declares environment-variable requirements in metadata but does not define an explicit tool/permission scope. That creates an authorization and transparency gap: an agent or reviewer cannot easily tell what sensitive resources the skill expects to access, increasing the risk of unintended secret exposure or over-broad execution in permissive runtimes.
The natural-language content from L09 onward is presented in Chinese, including setup and usage instructions, with no indication that the skill is region-specific or that users can opt into another language. This can violate language/locale policy when a skill forces a specific language without user choice.
follow-redirects 1.15.11 is flagged for leaking custom authentication headers across cross-domain redirects. Because axios depends on this package and this skill likely accesses traffic or SCATS endpoints over HTTP(S), a malicious or compromised upstream service could potentially induce redirects that expose bearer tokens, API keys, or other sensitive headers to an attacker-controlled domain.
The dependency is specified with a caret range (^1.6.0), which allows installation of newer 1.x releases that may change over time and can unexpectedly introduce vulnerable versions or break reproducibility. In a skill that queries external traffic data over the network, a drifting HTTP client dependency increases supply-chain and patch-management risk.
"scats": "node scats.js"
},
"dependencies": {
"axios": "^1.6.0"
}
}
No suspicious patterns detected.