Docs
Protet docs
Start here. Pick the path that matches what you want to do; every page has commands you can copy and run.
Status: preview. The GitHub Action and the cloud path from a build to a verdict are being fixed. Do not rely on them for protection yet: a green result from the Action today does not mean your build was checked. Accounts, tokens, usage metering and the Protet Intel feed are live. Details are on each page.
Choose your path
Quickstart (5 minutes)
Create a free account, mint a token, check your usage and read the Intel feed.
GitHub Action
What the Action does, how to set it up and what it reports. Preview.
Install: on-prem
Run Protet in your own infrastructure: fetch the signed bundle, license and keys.
Protet Intel feed
Confirmed malicious npm packages as OSV, Atom and NDJSON, with curl examples.
Reference
Configuration reference
Action inputs, environment variables, Helm values, limits and retention.
API reference
Public endpoints: account, tokens, usage, public keys and the Intel files.
Integrations
The OCSF finding schema, ingest authentication and the ingest event shape.
GitHub Action reference
The full workflow YAML, every input, the secret, permissions and runner support.
Troubleshooting
401, 422, 429, an Action that stays quiet, bundle pulls and installs.
Security and privacy
- How it works: what Protet collects, what it flags and what you receive.
- Security: how data is handled in each deployment mode, and how to report an issue (hello@protet.io).
- Plan limits and plan questions: Pricing.
- Privacy, DPA and Terms.
- Retention in the cloud: build activity is held for at most 24 hours, each build's result for up to 6 hours, and nothing is archived.