nicheclock@0.1.0
VERIFIED· not startedPublisher claims: "Enables AI assistants to query locally generated trend data from the last run, including rising topics by niche, upcoming dated events with publish-by dates, Search Console content gaps, and topic evidence for judging. It is read-only and does not fetch data, call a model, or write files." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try nicheclock` runs it now and prints the full answer.
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 (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-07 and scored it 85/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 · 2 scenarios · 0 deviationsStatic findings
&& mkdir -p /nicheclock && chown nicheclock:nicheclock /nicheclock \Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.stop() { kill $SERVER $RUNNER 2>/dev/null || true; wait 2>/dev/null || true; exit 0; }Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.&& chmod 0755 /usr/local/bin/docker-entrypoint.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.# mkdir -p nicheclock-data && cp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.kill -0 $SERVER 2>/dev/null || { echo "report server stopped; exiting" >&2; exit 1; }Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.if [ -n "$RUNNER" ] && ! kill -0 $RUNNER 2>/dev/null; thenFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// npx wrangler d1 execute nicheclock --local --file mint.sql # local devFix: Pin versions and sources; vendor anything fetched at install time.r = subprocess.run(["bash", "-n"], input=block.text, text=True, capture_output=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.docker compose --env-file .env.example config -qFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."https://example.com/sitemap-posts.xml": "sitemap_posts.xml",Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.# Run as the owner of ./nicheclock-data on the host. Set NICHECLOCK_UID / NICHECLOCK_GID in .env if `id -u` is not 1000.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.step "compose files parse (with and without the ollama profile, and with .env.example as the env file)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- path: .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// npx wrangler d1 execute nicheclock --remote --file mint.sql # production (needs the Cloudflare token)Fix: Pin versions and sources; vendor anything fetched at install time.nicheclock = ["onboard/data/*.json.gz", "onboard/data/*.json", "llm/prompts/*.md", "i18n/*.json", "output/app/*", "catalog/data/*.json", "catalog/data/*.yaml"]Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.subprocess.run(["openssl", "req", "-x509", "-newkey", "rsa:2048", "-nodes", "-keyout", str(key),Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.