cred-1@2026.11.10
VERIFIED· install onlyPublisher claims: "Checks the credibility of news domains against the open CRED-1 dataset of 2,600+ rated domains, aggregated from OpenSources and Iffy.news. Tools to check one domain, batch check, search, and read dataset stats and categories; no API key needed." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
GOOGLE_API_KEY- Where it talks to
- no vendor host named in the codeAlso iffy.news, githubusercontent.com, google.com, tranco-list.eu, rdap.org, infowars.com, no-color.org — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names iffy.news, githubusercontent.com, google.com, tranco-list.eu, rdap.org, infowars.com, no-color.org as well as its own vendor. The guard injects GOOGLE_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-13 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.* npx -y @aloth/cred1 --mcpFix: Pin versions and sources; vendor anything fetched at install time.- run: npm install -g npm@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.const r = spawnSync(process.execPath, [cli, ...args], { encoding: 'utf-8', env: { ...process.env, ...env } });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.