About
About Protet
Protet detects supply-chain attacks in npm CI/CD builds. It is independent and founder-led.
Why Protet exists
A CI/CD runner holds registry credentials, cloud roles and signing keys, often more privilege than the production workloads it builds. Supply-chain security tools mostly check what a build declares: a lockfile, an SBOM, a manifest. They do not see a postinstall script that turns malicious when the build runs it, or an attacker running commands with a stolen CI credential.
Protet watches what a build actually executes and flags the sessions that don't belong. How it works describes the product, and Protet Intel shows what it finds in newly published npm packages every day.
Who builds it
Protet is built and run by Robin Frehner. By day he works in cyber security, building malware detection. Protet applies that same discipline to what CI/CD build sessions execute.
The person who built the detection is the person who answers your email. There is no support tier and no account manager in between.
Contact
- hello@protet.io
- GitHub
- github.com/protet
- Robin Frehner
- LinkedIn (company)
- Protet
Questions about your environment, security reviews or on-prem deployments: email us and you reach Robin directly.