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

@alfe.ai/config

v0.4.1

Published

Read and write `~/.alfe/config.toml` for Alfe CLI, gateway, runtimes, and published plugins.

Readme

@alfe.ai/config

Read and write ~/.alfe/config.toml for Alfe CLI, gateway, runtimes, and published plugins.

What It Does

Shared config management for the Alfe user-side tools (CLI, gateway daemon, plugins). Reads and writes the user's local config file at ~/.alfe/config.toml.

  • readConfig() — read and parse ~/.alfe/config.toml
  • writeConfig(config) — write config to ~/.alfe/config.toml
  • configExists() — check if config file exists
  • resolveConfig() — resolve environment overrides, file values, runtime, workspace, API origin, and voice HTTP origin
  • getEndpointFromToken(token) — derive API endpoint from token prefix (alfe_dev_, alfe_test_, alfe_live_)
  • mergeAndWriteConfig(partial) — atomically update owned top-level fields without deleting runtime tables
  • writeRuntimeConfig(name, config) — atomically update one runtime table

Config Format

# ~/.alfe/config.toml
api_key = "alfe_live_xxxx..."
gateway = "https://api.alfe.ai"  # optional override
gateway_url = "wss://gateway.alfe.ai/ws" # optional daemon relay override
runtime = "openclaw"

[runtimes.openclaw]
workspace = "/home/alfe/.openclaw"

Resolution precedence is ALFE_API_KEY / ALFE_API_URL, then the config file, then token-prefix endpoint derivation. Plaintext HTTP/WS overrides are accepted only for loopback development. The credential file is atomically replaced with mode 0600 inside an owner-only ~/.alfe directory; concurrent writers are serialized across processes.

writeConfig() intentionally replaces the complete document. Commands that own only a subset must use mergeAndWriteConfig().

Development

pnpm install
pnpm --filter @alfe.ai/config lint
pnpm --filter @alfe.ai/config typecheck
pnpm --filter @alfe.ai/config test
pnpm --filter @alfe.ai/config build

Dependencies

  • smol-toml — TOML parsing and serialization

Links