Repository navigation
Clarify first detection and monitor-mode installation - #67
Merged
Merged
Conversation
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
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 README promises automatic 403 responses even though the adapters default to monitor mode. Clarify the actual behavior, replace absolute zero-false-positive claims, and put the installation and verification paths near the top.
Add a local tripwire check that reads
req.webdecoyDecisioninstead of treating the HTTP status as a detection verdict. Link Express docs and the optional dashboard with GitHub campaign parameters; keep local keyless rules distinct from cloud reporting.Validation: checked default mode and decision properties against
packages/express/src/middleware.ts, the decision API, and AGENTS.md; reviewed Markdown anchors and whitespace. Documentation only; no runtime behavior changed.