Get Ravenstash support
Start with the troubleshooting guide and the publish or install page for your ecosystem.
Contact support
Section titled “Contact support”Email [email protected] when the documented checks do not resolve the problem.
Include:
- Personal account or organization name.
- Repository name and selected ecosystem.
- Package-manager and version.
- UTC time of the request.
- HTTP status and complete client error text.
- Sanitized
rvscommand with credentials removed. - Whether the issue affects publishing, installation, a private mirror, the app, or
rvs. - Whether the same operation works from another computer or network.
Never send secrets
Section titled “Never send secrets”Do not email API-token values, passwords, refresh tokens, passkey data, token-bearing URLs, private package contents, or unredacted CI logs. Ravenstash support does not need the API-token secret to identify its metadata.
Suspected credential exposure
Section titled “Suspected credential exposure”Rotate the token or revoke the device session before collecting diagnostics. Remove the exposed value from active CI configuration, then review logs and package activity for unexpected access.
Repository restoration
Section titled “Repository restoration”Contact support within seven days of eligible repository deletion. Provide the account or organization, namespace, repository name, and the stable repository ID shown in the app. Restoration is unavailable after the recovery window and should not be used as a backup strategy.