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

@vanhecke/celmex

v3.0.0

Published

CLI for the Cortex Platform REST API, built on the vanhecke/celmex Elm SDK

Readme

celmex

Elm SDK and CLI for the Cortex Platform REST API.

Elm library

Install:

elm install vanhecke/celmex

Use:

import Cortex.Client exposing (Config, send)
import Cortex.Auth exposing (Credentials)
import Cortex.Api.AuditLogs as AuditLogs

config : Config
config =
    { tenant = "https://api-yourfqdn.xdr.eu.paloaltonetworks.com"
    , credentials = { apiKeyId = "...", apiKey = "..." }
    }

-- Send a request
send config GotAuditLogs (AuditLogs.search AuditLogs.defaultSearchArgs)

Every list/search endpoint takes a SearchArgs record carrying optional filters, sort, pagination, timeframe, and an extra escape hatch — see Cortex.Query for the filter/sort DSL and Cortex.RequestData for the shared envelope.

CLI

One-off (no install):

export CORTEX_TENANT_URL="https://api-yourfqdn.xdr.eu.paloaltonetworks.com"
export CORTEX_API_KEY_ID="..."
export CORTEX_API_KEY="..."

npx @vanhecke/celmex healthcheck
npx @vanhecke/celmex audit-logs search

Persistent install (adds cortex to your PATH):

npm install -g @vanhecke/celmex
cortex audit-logs search

Environment contract

| Variable | Purpose | |---|---| | CORTEX_TENANT_URL | Your tenant API base URL | | CORTEX_API_KEY_ID | Advanced API key ID | | CORTEX_API_KEY | Advanced API key secret |

Development

cp .envrc.example .envrc    # fill in credentials, then: source .envrc
npm install
just build                  # format + compile cli/dist/elm.js
just test                   # run BATS integration tests against a real tenant
just cli healthcheck        # rebuild if needed, then invoke ./cli/bin/cortex
just clean                  # remove build artifacts

Releasing

just publish 1.0.1          # bump elm.json + package.json, tag, push, publish both