VS Code Extension
View package diagnostics, attestations, and policy feedback directly in your editor.
-
Install from the Marketplace
Phylax VerifiedInstallView package trust, attestations, and policy feedback in VS Code.
Or from the Command Palette: Extensions: Install Extensions, then search
Phylax. -
Authenticate
Sign in to your Phylax account from the Command Palette, or run:
Terminal window phylax auth loginThe extension reuses your Phylax CLI session, so if you have already authenticated in a terminal there is nothing more to do.
-
What the extension shows
Inline diagnostics See trust verdicts directly in your code for packages inpackage.jsonand manifests.Hover insights Hover a package to view attestations, provenance, and risk details.Problems panel findings All policy violations and issues are surfaced in the Problems panel for quick action. -
Recommended settings
.vscode/settings.json {"phylax.enable": true,"phylax.scanOnOpen": true,"phylax.policyLevel": "moderate","phylax.showInlineResults": true,"phylax.autoUpdate": true}Commit this file to share one configuration with the whole team.
policyLevelacceptslenient,moderateandstrict; it controls which verdicts become Problems panel entries, not what Phylax checks. -
Quick example
Open a manifest and the extension annotates each dependency in place.
package.json {"name": "demo-app","version": "1.0.0","dependencies": {"express": "^4.18.2","left-pad": "^1.3.0"}}- express@4.18.2:
- trusted
- integrity:
- verified
- license:
- MIT
- risk:
- low
What WARN means- left-pad@1.3.0:
- policy violation
- status:
- deprecated package
- maintenance:
- no recent activity
The extension resolves ^4.18.2 against your lockfile, not against the range, because the
range is not what ships. If a verdict here disagrees with one from CI, check that your
lockfile is committed and current.
Related guides
For the same verdicts while browsing, see the Chrome Extension. To enforce them on every build, see CI/CD Pipelines.
The extension is open source at praxi-labs/phylax-vscode.