vscode-uri

The URI implementation that is used by VS Code and its extensions

vscode-uri@3.2.0 was published on 2026-08-24. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All vscode-uri versions · Permanent reference to 3.2.0

Package specifications

Version3.2.0
License declarationMIT
Published2026-08-24T22:41:22.545Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size199.97 KiB
Published file count17
Package typeNot declared
ES module entryNot declared
Default entry./lib/umd/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies0
Repository stars263
Repository forks35

Install vscode-uri 3.2.0

npm install vscode-uri@3.2.0
pnpm add vscode-uri@3.2.0
yarn add vscode-uri@3.2.0

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

    How to interpret the specifications

    Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

    Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

    OpenSSF repository checks

    Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

    Maintained8/10 — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
    Binary-Artifacts10/10 — no binaries found in the repo
    Code-Review10/10 — all changesets reviewed
    Security-Policy10/10 — security policy file detected
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    Branch-Protection8/10 — branch protection is not maximal on development and all release branches
    SAST4/10 — SAST tool is not run on all commits -- score normalized to 4

    Evidence and freshness