Your dependency graph,
fully resolved
Trace every package back to why it exists. Inspect how specifications resolve, surface affected transitive dependencies, and query it all with a selector syntax built for JavaScript.
Understand
every dependency
Explore your project’s fully resolved dependency graph (no theoretical SBOMs here). Trace why a dependency exists, inspect how specifications resolve, identify affected transitive packages, and query the graph with a powerful selector syntax designed specifically for JavaScript dependencies.
$vltconfigsetregistry=https://registry.vlt.io/acme/npm/
Config updated
$vltlogin
Logged in successfully
$vltinstall
$
Explore
Browse private packages and upstream mirrored npm packages
Setup instructions$vltquery[name^=cookie]
project
└─┬ express@5.2.1
├── cookie@0.7.2
└── cookie-signature@1.2.2
$
Trace
See why and how dependencies were resolved
Learn more$vltquery:fs
project
├─┬ express@5.2.1
│ ├── etag@1.8.1
│ ├─┬ send@1.2.1
│ │ └── etag@1.8.1
│ └─┬ serve-static@2.2.1
│ └── send@1.2.1
$
Query
Identify packages using Dependency Selector Syntax
Query documentation✓ :malware - 0 results
✓ :vulnerable - 0 results
✓ *:license(copyleft) - 0 results
✓ :deprecated - 0 results
✗ :root > * - 28 results
Failed: 1 of 5 queries did not
meet expectations
$
Control
Convert those queries into policies and graph transformations
Policies