VSLOC

VSLOC measures a workspace without sending its source anywhere. It shows a compact status-bar headline and native Explorer tree with physical, code, comment, blank, file, and byte totals.

The interface uses native status and tree controls, theme-aware icons, explicit state/accessibility labels, and keyboard-invokable scan, cancellation, paging, file-open, and recovery actions. English manifest and runtime localization source bundles are included so translations can be added without restructuring UI strings. Actual screen-reader, keyboard focus-order, translated-locale, zoom, and high-contrast qualification remains part of the release checklist.

Use

Open a folder.
Select the VSLOC: Scan Workspace command or click VSLOC: Scan in the status bar.
Expand Project Size in Explorer for language, category, folder, directory, file, and exclusion details.
With a workspace file open, run VSLOC: Explain Current File—or use Explain Current File on a VSLOC file row—to see the retained selection rule, language/category provenance, measurement outcome, and freshness without rereading source.
Run VSLOC: Create Configuration to add a validated .vslocrc.jsonc.

The first scan is explicit. After a successful scan, file changes update incrementally when vsloc.scan.watch is enabled.

Develop in VSCodium

Install dependencies and build:

npm ci
npm run check
npm run build

Open this directory in VSCodium, switch to Run and Debug, choose Run VSLOC Extension, and press F5. The Extension Development Host opens the basic fixture. Run VSLOC: Scan Workspace there.

To test the installable artifact:

npm run package
codium --install-extension vsloc-0.1.0.vsix --force

For the stronger isolated-profile journey on Linux, pass the VSCodium Electron binary separately from its CLI wrapper (replace the application path for your installation):

npm run test:vsix -- --editor /path/to/VSCodium --editor-cli "$(command -v codium)" --vsix ./vsloc-0.1.0.vsix

That gate uses the exact installed VSIX in fresh profiles. Release qualification verifies the normal production install exposes no test API, measures 20 isolated shell activations with a strict p95 under 50 ms, then requires the deferred native runtime and cache-manifest initialization to reach readiness within 100 ms p95. Workspace-I/O counters are sampled only after that barrier and must still be zero before an explicit scan. The journey then checks exact totals in an untrusted workspace and requires create, change, rename, and delete updates to become visible within 750 ms. Machine-readable evidence is written to bench/generated/installed-vsix-evidence.json; use --evidence-output PATH to preserve it elsewhere. Ordinary CI uses --quick as an explicitly exploratory hosted-runner check: it samples five fresh processes, gates the extension-owned activation body below 50 ms and deferred readiness below 150 ms, and cannot emit release-qualified evidence.

For a faster local harness check, append --quick. It runs two isolated activation samples and the complete functional journey, but its evidence is explicitly exploratory and cannot qualify a release lane. The default 20-sample run can qualify one lane; the release workflow still requires a complete, same-SHA desktop evidence set plus the external/manual checklist.

Reload VSCodium, open a real project, and invoke VSLOC: Scan Workspace. Uninstall the development build with:

codium --uninstall-extension 0xbenc.vsloc

Configuration

Project rules live in one .vslocrc.jsonc at each workspace-folder root. Run VSLOC: Create Configuration rather than writing one from memory; VSCodium provides validation and completion from the schema bundled in the extension.

See configuration, counting semantics, and privacy.

Compatibility

The MVP targets desktop VS Code/VSCodium and Node-backed remote extension hosts. Standalone browser and arbitrary virtual workspaces are not yet declared supported.

License

MIT