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

@mythral0/workflow-bootstrap

v0.1.1

Published

Generate tested GitHub Actions and GitOps workflows from an existing repository

Vulnerabilities

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

Links

Git

Maintainers

mythral0mythral0

Keywords

github-actionsgitopsworkflowbootstrapdockerhelm

Readme

Workflow Bootstrap

Generate a consistent, test-gated GitHub Actions and GitOps delivery pattern from an existing repository.

npx @mythral0/workflow-bootstrap init

The command detects the project runtime, package manager, available checks, Docker build targets, Helm charts, and staging/production values files. It then writes a committed .workflow-bootstrap.yml and thin project workflows that call mythral0/platform-workflows.

Supported detection

  • Node.js with npm, pnpm, or Yarn
  • Python projects
  • Go modules
  • .NET solutions and projects
  • Generic Makefile checks
  • One or many Dockerfiles and terminal multi-stage targets
  • Helm values-staging.yaml and values-live.yaml image tag paths

Detection creates a starting point; the manifest is the source of truth. Edit it when a repository has custom commands or non-standard deployment paths.

Commands

# Detect and initialize the current repository
npx @mythral0/workflow-bootstrap init

# Non-interactive initialization
npx @mythral0/workflow-bootstrap init --yes

# Regenerate after editing the manifest
npx @mythral0/workflow-bootstrap sync

# Validate the manifest and generated files
npx @mythral0/workflow-bootstrap check

init does not overwrite conflicting files unless --force is supplied. sync intentionally rewrites generated files from the committed manifest.

Delivery behavior

  • Pull requests run quality checks.
  • Merges to main rerun checks before building images.
  • Staging pipelines are serialized and cannot overlap.
  • A stale build cannot promote after main advances.
  • GitOps values are committed only after successful image builds.
  • GitHub Releases build immutable versioned images.
  • Production promotion remains a separate manual workflow.
  • Deployment controllers reconcile Git; Actions do not connect to clusters.

Configuration

The generated .workflow-bootstrap.yml contains all detected CI commands, container components, registries, and GitOps update expressions. Repositories with different component layouts receive different build matrices.

Requirements

  • Node.js 20 or newer for the bootstrap command
  • GitHub Actions for generated workflows
  • GHCR for the initial 0.x container workflow
  • A GitOps controller watching the configured branch for deployment

License

MIT