Security audit
Security checks for vulnerabilities and agentic risk
The skill is a news digest server, but its documentation contradicts itself about whether state-changing API endpoints require authentication.
Review this skill carefully before installing or exposing it. If used, keep the API bound to localhost or behind trusted access control, and require authentication or an API key for all POST, PUT, DELETE, and configuration endpoints before deploying it beyond a private environment.
The documentation states the tool runs in read-only mode and that write features require credentials, but it also documents unauthenticated POST /api/digests and PUT /api/config endpoints. This mismatch can mislead operators into deploying the service with unsafe assumptions, leaving system-changing functionality exposed without access control.
The auth/credentials section says digest creation requires an API key and auth features require credentials, but the endpoint table marks mutating endpoints as unauthenticated. That contradiction increases the likelihood of accidental exposure of privileged functionality and suggests broken or undocumented access-control expectations.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
npm install
# Copy environment config
cp .env.example .env
# Edit .env with your settings
# Start API server
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
npm install
# Copy environment config
cp .env.example .env
# Edit .env with your settings
# Start API server
The documented API exposes state-changing endpoints, including digest creation and configuration updates, without indicating authentication or warning users that they modify server state. In skill context, this is dangerous because users may invoke those endpoints assuming they are safe read operations, enabling unauthorized changes or abuse of backend resources.
No suspicious patterns detected.