Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md node scripts/github-search.mjs "keywords" --language js --min-stars 50 --limit 5
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a GitHub repository search helper whose network and token behavior matches its stated purpose.
Install only if you are comfortable with project search terms and selected repository names being sent to GitHub. If GITHUB_TOKEN is set in the agent environment, the scripts will use it for GitHub API rate limits, so use a least-privilege token or unset it when unnecessary.
Referenced artifact was not completely inspected
node scripts/github-search.mjs "keywords" --language js --min-stars 50 --limit 5
Referenced artifact was not completely inspected
node scripts/repo-detail.mjs "owner/repo"
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
Returns detailed repo info (README excerpt, topics, latest release, etc.) as JSON
with `status: "ok"`. On failure: `{"status":"error","code":"...","message":"..."}`.
## Display rules
- `stars: 12300` → "12.3k" (or "1.23万" in Chinese)
- `pushed_days_ago: 3` → "3 days ago" / "3天前"
The skill instructs use of shell commands, network access to GitHub, and environment-based authentication via GITHUB_TOKEN, but it declares no explicit tool scope or permissions boundaries. That creates an avoidable over-privilege and transparency problem: an agent may execute external commands or use sensitive environment data without a clear allowlist, increasing the risk of unintended command execution, token exposure, or broader tool access than the task requires.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
* Uses Node's built-in fetch (no curl / shell dependency, no command injection).
*/
const GITHUB_API = 'https://api.github.com/repos';
function parseArgs() {
const args = process.argv.slice(2);
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
* Uses Node's built-in fetch (no curl / shell dependency, no command injection).
*/
const GITHUB_API = 'https://api.github.com/repos';
function parseArgs() {
const args = process.argv.slice(2);
This code sends the constructed query to the external GitHub Search API via fetch, which transmits user-provided input off-system. Although the file documents that it uses fetch, it does not clearly disclose to the user that their query is sent to GitHub, and there is no confirmation prompt or user-facing notice at runtime.