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

@terragonstudios/atlas-core

v1.0.4

Published

## Webhook Ingress (local)

Downloads

31

Readme

Atlas Core

Webhook Ingress (local)

  • Endpoint: POST http://localhost:3000/webhook
  • Auth: require x-atlas-webhook-secret: <secret>; this is the only accepted auth header (Authorization is ignored).
  • Secret: set ATLAS_WEBHOOK_SECRET in all non-local environments. If unset and NODE_ENV is not production, the expected secret defaults to atlas-dev-secret (dev only). In production with a missing secret, all requests will 401.
  • Response codes: 202 means the payload was validated and accepted into processing (queued/handed to the core); downstream work may still be async and may fail later (e.g., rules/timers). 401 means missing/wrong secret.
  • Payload schema: must match AtlasEventSchema (eventId, eventType, occurredAt ISO string, source, propertyId, unitId, issueId, payload). All fields are required; payload defaults to {} if omitted.
  • Enums (case-sensitive): eventType one of IssueCreated, IssueUpdated, IssueClassified, IssueClosed, VendorDispatched, VendorAccepted, VendorDeclined, VendorArrived, VendorNoResponseDetected, JobCompleted, SLATimerStarted, SLATimerBreached, ProofMissingDetected, RuleConflictDetected, EscalationTriggered. source one of PMS, Atlas, VendorPortal, Simulator.
  • Optional debug logging: set DEBUG_WEBHOOK=true to log accepted webhook event metadata.
  • Optional simulator feed in hybrid runner: set RUN_SIMULATOR=true to also replay the sample events; otherwise hybrid waits for webhooks only.

Example (uses default dev secret):

curl -X POST http://localhost:3000/webhook \
  -H "x-atlas-webhook-secret: atlas-dev-secret" \
  -H "Content-Type: application/json" \
  -d '{"eventId":"demo1","eventType":"IssueCreated","occurredAt":"2024-01-01T00:00:00.000Z","source":"Simulator","propertyId":"TEST","unitId":"1-01","issueId":"ISSUE-1","payload":{"category":"GENERAL","priority":"STANDARD","afterHours":false,"occupied":true}}'

Runner commands

  • Webhook-only hybrid (no simulator): DEBUG_WEBHOOK=true npm run atlas:hybrid
  • Simulator + webhook hybrid: DEBUG_WEBHOOK=true RUN_SIMULATOR=true npm run atlas:hybrid

You can omit DEBUG_WEBHOOK if you don't want ingress debug logs. The hybrid runner still polls the provider; with RUN_SIMULATOR=true it also seeds the sample events before polling.

Testing

  • Run tests with coverage: npm test (Vitest, with coverage thresholds configured).

CI

  • Tests run on every push and pull request via GitHub Actions.
  • Local check: npm test.