Help
Troubleshooting
Real error messages, their causes, and how to fix them.
These are the messages the product shows, taken from the source code.
| Message | Cause | Fix |
|---|---|---|
Paste the advisory text (at least 40 characters) | The pasted advisory is empty or too short | Paste the full advisory, including affected versions |
Advisory text is limited to 12000 characters | The pasted text is too long | Remove unrelated sections such as references and credits |
Rate limited, try again in a minute | Too many requests from your address or overall | Wait one minute |
SERV Reasoning call failed: … | SERV returned an error, timed out, or returned invalid JSON | Try again; the rest of the message gives SERV’s reason |
Enter a public GitHub repository link, like https://github.com/owner/repo | The link could not be parsed | Use one of the forms in Choose which apps to check |
Repository not found. Pich can only read public GitHub repositories. | The repository is private, misspelled, or the branch does not exist | Check the link in a logged-out browser |
GitHub's rate limit for anonymous reads was hit. Try again in a few minutes. | GitHub limits unauthenticated reads | Wait a few minutes |
This package.json does not depend on next. Pich only checks Next.js apps. | The root is not a Next.js app, often a monorepo root | Link to the app folder with /tree/<branch>/<path> |
Everything says Needs manual review
Usually the version or hosting is unknown. Check whether the repository uses pnpm, yarn, or Bun, and whether it has a pich.deploy.json. See Limitations.