Support
A reproducible miss or a false signal is the most useful thing you can send. GitHub issues are the fastest route; email works too.
Open an issue
Each link opens the matching issue form. Please search existing issues first.
What to include
- The package version, Action ref, or commit.
- Node.js version, OS, language, and how you ran it: CLI, Action, or MCP host.
- The command, the relevant output, and what you expected.
- For drift findings: the symbol, its before and after signature, the doc path and section, and why the result is wrong.
A small synthetic repository and staledocs plan --json are often enough to reproduce an analysis issue.
Issues are public. Remove keys, tokens, private source, and personal data before posting.
Guides and common fixes
- GitHub Action guide: workflow, permissions, and forks.
- Claude Code guide: plugin install, manual MCP setup, and the safe update sequence.
- Codex / MCP guide.
- CLI reference and limitations.
No comment on a fork pull request? Check the job summary. Fork tokens are often read-only; the analysis still runs.
Switched repositories in your assistant? Start a new session in that repository. A running MCP server stays bound to the worktree it started in.
Security reports
Please do not open public issues for vulnerabilities. Use GitHub private vulnerability reporting and see the security policy.
Questions, feedback, or interest in StaleDocs for your team: hello@staledocs.com.
StaleDocs is built by one independent developer, so support is best-effort with no guaranteed response time.