Conversation
The CLI shipped, went on npm, got a cli-tools command and a moshcode entry, and was documented in none of the places someone would look for it: crawlproof.com had no page, and the repo README did not mention it existed. The only writeup was inside the published package, which you have to install before you can read. /docs/cli covers install and auth, the five dashboard screens and their keys, stats, running an ad, and the bearer-token routes underneath, so anything that is not this CLI can call them too. It also states what the ROI numbers mean, because those are the figures someone will quote at somebody else: self-deal is not revenue, personal money is not business cost, everything is a monthly rate prorated onto the window, and the bank window is not the traffic range. Along with what the dashboard refuses to claim -- a site that did not answer is missing rather than zero, and a visitor is any non-crawler hit, which is why the per-pageview figure sits beside it. The README section says where the package comes from and that it is a build artifact of lib/dashboard/* rather than a second copy, so nobody edits the wrong one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvWJ4336pxTFRdRbvsTQeD
ThreatCrush Security Scan39 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 28 | LOW: 9
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CLI shipped, went on npm, got a cli-tools command and a moshcode entry, and was documented in none of the places anyone would look: crawlproof.com had no page for it, and the repo README did not mention it exists. The only writeup lived inside the published package, which you have to install before you can read it.
/docs/cliInstall and auth (including
~/.crawlproof.json, so nobody has to remember an export), the five dashboard screens and their keys,stats, running an ad, and the bearer-token routes underneath — so anything that is not this CLI can call them too.It also states what the ROI numbers mean, because those are the figures someone will end up quoting at somebody else:
and what the dashboard refuses to claim: a site that did not answer is missing rather than zero, and a "visitor" is any non-crawler hit, which is why the per-pageview figure sits beside the per-visitor one.
README
Says where the package comes from and that it is a build artifact of
lib/dashboard/*rather than a second copy, so nobody edits the wrong file. Plus the route table.Verified
Rendered against a local server on the production environment:
tsc --noEmitclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01HvWJ4336pxTFRdRbvsTQeD