Troubleshooting
Diagnose authentication and package resolution issues.
Check this device
Run scrutyn status and scrutyn doctor. The latter reports registry configuration without editing files. Do not paste credentials or credential-bearing package manager configuration output into tickets or agent sessions.
CLI exit codes
The CLI uses these exit codes for its own commands:
| Code | Meaning |
|---|---|
| 0 | Success. |
| 1 | The command found a problem, such as a blocked or unknown package. |
| 2 | Invalid arguments or a command requiring a terminal. |
| 3 | Authentication or authorization failed. |
| 4 | The API is unavailable or asked the client to retry later. |
| 5 | An internal error occurred. |
| 130 | Interrupted with Ctrl-C. |
Commands that run another program can return that program's exit code.
A package cannot be installed
Use scrutyn why npm example-package@1.2.3 or scrutyn why pypi example-package@1.2.3. A release may be in Lazaretto, held, blocked, missing or removed upstream. See blocked installs.
Authentication fails
Check that the device is logged in, has not been revoked or suspended, and is using the intended registry. After replacing a device token, run the relevant user setup again. Check for project overrides and extra indexes; never put a token in a committed file.
Emergency public-registry access
scrutyn bypass --for 1h --reason "reason" -- npm install requires an interactive human and server support. It warns that the command uses public registries without the service's scans, quarantine or install history. It is not available to agents and must not be treated as a security control; policy or server availability can refuse it.