The Phylax platform
How the Phylax platform verifies artifacts end to end.
Phylax is a security layer for the AI software supply chain. Agent skills, MCP servers, packages and repositories all execute code you did not write, and all of them reach your codebase through the same few doorways. Phylax sits in those doorways.
What it verifies
| Artifact | Example |
|---|---|
| Packages | pkg:npm/express@4.18.2, pkg:pypi/requests@2.32.3 |
| Repositories | everything a lockfile installs |
| MCP servers | the tools a server exposes to an assistant |
| Agent skills | code an agent loads and runs at its own discretion |
Each is identified by exactly what it is, pinned to a version. A verdict never spans versions, because a new release is new code.
How a verdict is produced
- Identify. The artifact is reduced to a content address, so identical bytes are the same artifact no matter where they came from or what they claim to be.
- Look up. If that artifact has already been analysed under the current analysis, the recorded verdict is returned. This is the common case and it is fast.
- Screen. Anything new is screened immediately, so you get an answer now rather than waiting.
- Analyse. New artifacts are analysed in depth by the network, and the result is recorded and signed as an attestation.
Because the record is keyed on both the artifact and the analysis behind it, improving the analysis retires the old results rather than leaving them to go stale unnoticed.
Where it plugs in
The same verification is reachable from wherever the decision actually happens:
- Before you commit with the CLI, so a risky package is caught before it enters the repository.
- In the editor with the VS Code extension, marking risky dependencies alongside your type errors.
- On the pull request with the GitHub App or the Action, failing the check before a merge.
- At runtime with the agent runtime gate, which verifies a tool before an agent is allowed to call it.
- While browsing with the browser extension, putting a verdict on npm, PyPI and GitHub pages before you install.
- Anywhere else through the SDKs and the REST API.
They all call the same API and return the same verdict, so a package blocked in CI is blocked in the editor too.
Access
Reading the public catalogue and public scores needs nothing. Verifying an artifact, reading full findings, evaluating policy and every SDK call need an API key on a paid plan. See where to get Phylax to install a client, and accounts and API keys to get a token.