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

@zenyangzzz/vesper

v0.1.0

Published

Agent-first CLI for authenticated remote log queries

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

zenyangzzzzenyangzzz

Keywords

Readme

Vesper CLI

An Agent-first CLI for querying authorized remote service logs through one Vesper Gateway. Installing the CLI does not grant access to any team or logs. The package contains no credentials, Feishu application secret, deployment configuration, or business logs.

Requires Node.js 24 or newer. This package exposes the vesper executable, not a JavaScript SDK. The Gateway operator supplies the approved HTTPS origin.

vesper config set-server https://vesper.example.com
vesper auth login --no-wait

Open the returned verification link and authorize in Feishu. Keep deviceCode private. Complete the same login before it expires:

vesper auth login --device-code '<deviceCode>' --no-wait
vesper auth status
vesper projects list
vesper services list --project '<project>'
vesper query --project '<project>' --service '<service>' --since 1h

A pending login is not a failure; wait at least its returned interval before polling again. The server requires an allowed Feishu tenant and project/service scope. Users who cannot authorize the Feishu application cannot complete this login. Public package availability does not bypass these checks.

Queries return all matches in the registered file by default. Optional --contains matches a case-sensitive message substring; --level sets the minimum level; --limit returns an explicitly requested count. There is no implicit scan-byte, lookback, or entry-count cap. File archives are not searched automatically. Query errors mean the query did not complete, not that no matching logs exist.

Success is one JSON object on stdout. Errors are JSON on stderr. Exit codes: 0 success, 2 invalid input/config, 3 authentication/access, 4 missing source, 5 server/network error, 1 other failure. Use vesper --help for commands.

Stored credentials live under ${XDG_CONFIG_HOME:-~/.config}/vesper/ and are origin-bound. Never share that directory or tokens. Service accounts can use VESPER_TOKEN only with matching VESPER_TOKEN_SERVER, as authorized by their Gateway operator. A token is a credential regardless of how the CLI was installed.