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

@albertomarturelo/nemo-cli

v0.2.0

Published

Human-facing CLI (`nemo`) for the Vector Capital portal. Each command is a thin call into @albertomarturelo/nemo-core tasks (ADR-003).

Readme

@albertomarturelo/nemo-cli

nemo — a terminal client for the Vector Capital broker portal (Chile). It automates the routine reads an account owner performs by hand: check the session, browse instruments, inspect the cartera. Every command is a thin call into @albertomarturelo/nemo-core, which owns token renewal, the audit receipt, and credential handling.

⚠️ Unofficial. Not affiliated with, endorsed, or sponsored by Vector Capital S.A. Corredores de Bolsa. Provided "as is" (MIT). Use it against your own account only. See the repo root README for the full disclaimer.

Install

npm i -g @albertomarturelo/nemo-cli

Requires Node.js >= 20.

Quick start

nemo auth login            # hidden password prompt; caches only the bearer token
nemo auth status
nemo instruments local --search BCI --limit 10
nemo cartera summary --human

Commands

| Command | What it does | | ---------------------------------------------------------- | --------------------------------------------------------- | | nemo auth login [--user <email>] | Sign in; cache the bearer token | | nemo auth status | Session state (local read — never touches the network) | | nemo auth logout | Drop the cached token | | nemo instruments local [--search] [--page] [--limit] | Chilean instruments, paged | | nemo instruments international [--search] [--exchange] … | International (US-listed) instruments, paged | | nemo instruments prices --id <idInstrumento> | ~1y daily price history with stats + sparkline | | nemo cartera summary [--account-id] [--currency] … | Holdings with computed P&L and totals by classification | | nemo cartera movements [--desde] [--hasta] [--account-id] | Cash movements over a date range, classified per kind | | nemo cartera saldo [--account-id] [--currency] [--fecha] | Cash balance per caja at a date, valued in one currency |

--help on any level lists the full flag set.

Output

JSON is the default — the CLI is a faithful façade over the core's data contract, so it pipes straight into jq. Pass --human for readable text. Results go to STDOUT; diagnostics go to STDERR.

nemo cartera summary | jq '.totals'

Exit codes: 0 success, 2 not authenticated (including an expired session), 3 login failed, 1 anything else.

Credentials

The password is entered at a hidden prompt — never a flag, environment variable, or argument — held in memory for a single sign-in, then discarded. Only the resulting bearer token is cached, in a per-user file under ~/.nemo/. No credential ever reaches an AI model: the sign-in path is exported only to this CLI, which is why the companion MCP server has no login tool.

See also