npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@harness-lens/cli

v0.0.5

Published

Command-line interface for deterministic Harness Lens analysis.

Readme

SPDX-License-Identifier: MPL-2.0 Copyright © 2026 Cristian Camargo Filho

Harness Lens

@harness-lens/cli

Terminal adapters for Harness Lens structural analysis. The native Rust binary under rust/ is the reference CLI; the existing TypeScript package remains available to npm users.

npx @harness-lens/cli scan . --profile coding-agent/v1
npx @harness-lens/cli scan . --json
npx @harness-lens/cli scan . --input-cost-per-million-tokens 2.5 --invocations 100 --cost-reference provider/model-input-rate
npx @harness-lens/cli tui .
npx @harness-lens/cli compare before.json after.json

scan and the initial overview renderer are functional. The first tui command renders the same overview without an interactive event loop. Tabs, persistence, and Git-revision snapshot loading are planned.

The JSON and native CLI reports expose exact-duplicate counts, per-source byte and token measurements, soft size/token budget findings, and—when configured— input cost per invocation and total input cost.

The native CLI reads the same evaluation settings from harness-lens.toml:

[evaluation]
invocations = 100
input_cost_per_million_tokens = 2.5
cost_reference = "provider/model-input-rate"

--ai never changes deterministic findings or metrics. Until an interpreter is configured, it emits a notice and preserves the report.

Bootstrap order: publish @harness-lens/[email protected] before this package.

The Rust CLI pins an immutable revision of the harness-lens/sdk, keeping filesystem and analysis behavior out of the terminal adapter.

Ecosystem

Development

npm install
npm test
npm run check

cd rust
cargo test --locked
cargo run -- --version

Native releases

The release pipeline builds native macOS, Windows, and Linux archives with SHA-256 checksums, CycloneDX SBOMs, and signed GitHub attestations. Those same reviewed archives drive the Homebrew, WinGet, Scoop, and Chocolatey packages; the GHCR scanner image is published last. See docs/distribution.md for the exact artifacts, review gate, registry handoffs, container restrictions, and retention policy.

Language package placeholders

Buildable staging packages for the future Go and C/C++ implementations live in placeholders/. They document what can actually be reserved in each ecosystem and are intended to move into dedicated repositories before their first public release.

License

Early namespace-reservation versions used BSD-3-Clause. The official functional implementation is licensed under MPL-2.0. When Covered Software is distributed, modified MPL-covered files must remain available in Source Code Form under the license. See LICENSING, COPYRIGHT, and TRADEMARKS.