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

@nano-rs/dac-github-action

v0.1.0

Published

GitHub Action for NanoSIEM detection-as-code

Readme

NanoDac GitHub Action

Validate and deploy NanoSIEM detection rules via GitHub Actions.

Features

  • Validate detection files on pull requests
  • Deploy detections on merge to main
  • PR Comments with validation results
  • Dry-run mode to preview changes
  • Delete orphans option for full sync

Usage

Basic Workflow

name: Detection Sync

on:
  push:
    branches: [main]
    paths: ['detections/**']
  pull_request:
    paths: ['detections/**']

jobs:
  sync:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Sync detections
        uses: ./nanodac/packages/github-action
        with:
          nanosiem-url: ${{ secrets.NANOSIEM_URL }}
          api-key: ${{ secrets.NANOSIEM_API_KEY }}
          action: ${{ github.event_name == 'push' && 'both' || 'validate' }}
          github-token: ${{ secrets.GITHUB_TOKEN }}

Inputs

| Input | Description | Required | Default | |-------|-------------|----------|---------| | nanosiem-url | NanoSIEM API URL | Yes | - | | api-key | NanoSIEM API key | Yes | - | | search-url | Search service URL | No | - | | detections-dir | Directory containing detection files | No | detections | | action | Action: validate, deploy, or both | No | both | | strict | Treat warnings as errors | No | false | | dry-run | Preview changes without deploying | No | false | | delete-orphans | Delete remote detections not in local files | No | false | | github-token | GitHub token for PR comments | No | github.token |

Outputs

| Output | Description | |--------|-------------| | validation-result | valid or invalid | | created-count | Number of detections created | | updated-count | Number of detections updated | | deleted-count | Number of detections deleted |

Secrets

Add these secrets to your repository:

  • NANOSIEM_URL - Your NanoSIEM API URL (e.g., https://nanosiem.example.com:3000)
  • NANOSIEM_API_KEY - API key with detection permissions
  • NANOSIEM_SEARCH_URL - (Optional) Search service URL

PR Comments

When running on a pull request with github-token provided, the action posts a comment with validation results:

## Detection Validation Results

| Status | Count |
|--------|-------|
| ✅ Valid | 5 |
| ⚠️ Warnings | 1 |
| ❌ Errors | 0 |

### Warnings

**detections/risky_rule.yaml**
- ⚠️ mitre: No MITRE ATT&CK mappings specified

Example Workflows

See examples/workflows/ for complete workflow examples:

  • detection-sync.yml - Basic validate on PR, deploy on merge
  • detection-pr-review.yml - Detailed PR review with dry-run
  • detection-full-sync.yml - Full sync with orphan deletion