Feed Watcher

v0.0.1

Monitor RSS/Atom feeds and send notifications when new content appears. Track YouTube channels, Reddit subreddits, GitHub releases, blogs, and any RSS/Atom f...

1· 353·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description match the code: the CLI monitors RSS/Atom feeds, persists state, and can POST notifications to a webhook. That capability is coherent with the stated purpose.
Instruction Scope
SKILL.md instructs creating a .env with WEBHOOK_URL, USER_AGENT, and optionally DATA_DIR, and describes storage at ~/.feed-watcher/feeds.json. The code reads WEBHOOK_URL and writes state under the user's home directory, but it ignores USER_AGENT and DATA_DIR env vars. The SKILL.md also recommends installing 'rss-parser' and 'dotenv', but the runtime code does not use them. These are mismatches (likely bugs or sloppy docs) but they do not directly indicate exfiltration or extra-scope behavior.
!
Install Mechanism
There is no install spec, but package.json lists dependencies (rss-parser, dotenv, node-fetch) and SKILL.md suggests running 'npm install'. The shipped index.js does not import those modules (it uses only built-in http/https/fs/path). Asking users to run 'npm install' would pull packages (and their transitive dependencies and install scripts) from the public registry for no clear reason — unnecessary dependency installation increases supply-chain risk.
!
Credentials
SKILL.md documents WEBHOOK_URL and DATA_DIR (and mentions USER_AGENT) but index.js uses only WEBHOOK_URL and ignores DATA_DIR and USER_AGENT. The only environment access the program actually performs is reading WEBHOOK_URL and HOME/USERPROFILE to locate ~/.feed-watcher. The skill asks users to create a .env with values the runtime doesn't use, creating potential confusion. Requiring npm install (see above) requests broader implicit privileges (network access to npm) that are disproportionate to the code's actual needs.
Persistence & Privilege
The skill stores state in ~/.feed-watcher/feeds.json and does not request always:true or modify other skills/configs. It neither requires system-wide privileges nor persists beyond the user's home directory. That behavior is consistent with its purpose.
What to consider before installing
This skill appears to do what it says (poll feeds and send webhook notifications) but there are several inconsistencies you should consider before installing/running it: - The repository/package.json declares dependencies (rss-parser, dotenv, node-fetch) and the docs tell you to run 'npm install'. The provided runtime (index.js) does not import or use those packages. Installing them would pull code from npm (and possibly run package install scripts) for no functional reason — avoid running 'npm install' unless you audit those packages first. - The SKILL.md documents environment variables USER_AGENT and DATA_DIR, but the program ignores them. Only WEBHOOK_URL is actually read. Expect the documentation to be inaccurate; double-check that your webhook URL is safe and that you understand where state files will be written (~/.feed-watcher/feeds.json). - There is a small bug in the HTTP header keys in index.js (the 'Accept' header is malformed due to a typo). This is likely harmless but indicates the code may be lightly tested. Recommended steps before use: 1) Inspect index.js locally (you already have it) and confirm it meets your needs. It uses only built-in Node modules (http/https/fs) — you can run it without installing external deps. 2) If you must run 'npm install', do so in an isolated environment (container or VM) and review package.json and the npm packages to avoid unnecessary supply-chain exposure. 3) If you want USER_AGENT or custom DATA_DIR behavior, either adjust index.js yourself or request a corrected release. Also fix the malformed header key if necessary. 4) Consider running the tool with a non-privileged user account and monitor network calls the first time it runs. Given the mismatches (unused dependencies, inaccurate docs, and minor bugs) I rate this suspicious rather than benign. If the author can confirm why npm deps are listed and update docs to match the runtime, the assessment could move to benign.

Like a lobster shell, security has layers — review code before you run it.

latestvk977xv05v3cact8xhyhfmmhman825at2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments