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

@exayard/cli

v0.2.0

Published

Official CLI for the Exayard API

Vulnerabilities

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

Links

Maintainers

bfischer1121bfischer1121linh1211linh1211

Keywords

Readme

@exayard/cli

Official command-line interface for the Exayard API — AI-powered construction takeoffs, estimates, and bids. Built for humans and agents alike: every command supports --json for machine-readable output and returns stable exit codes.

Install

npm install -g @exayard/cli
# or run without installing:
npx @exayard/cli --help

Authenticate

Generate an API key with the minimum scopes you need at exayard.com/settings/developer, then:

exayard login --api-key sk_live_...

Credentials are saved to ~/.exayard/config.json. You can also pass --api-key / --org per call, or set EXAYARD_API_KEY.

Commands

Projects:
  exayard projects list --org org_...
  exayard projects create --name "<name>"
  exayard projects archive <project_id>

Webhooks:
  exayard webhooks list
  exayard webhooks create --url <https://...> --events "project.created,bid.generated"
  exayard webhooks delete <endpoint_id>
  exayard webhooks verify --signature ... --secret ... < body.json
  exayard listen --forward-to http://localhost:...   (experimental)

Help / misc:
  exayard help-search "how do I run a takeoff"
  exayard init                                       Drop agents.md into the cwd

Global flags

| Flag | Description | |------|-------------| | --json | Emit machine-readable JSON and suppress prose | | --api-key <key> | Override saved credentials for this call | | --org <id> | Override the saved organization ID |

Exit codes

| Code | Meaning | |------|---------| | 0 | Success | | 1 | Operation failed (expected, actionable) | | 2 | Usage error (bad flags) | | 3 | Network / unexpected error |

Agents should branch on the exit code and parse --json output.

Links

License

MIT