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

@kurocado-studio/styleguide

v2.7.1

Published

Kurocado Studio's engineering style guide

Downloads

474

Vulnerabilities

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

Links

Git

Maintainers

santiago132santiago132

Keywords

Readme

Kurocado Studio Engineering Style Guide

| Platform | URL | | ---------- | ----------------------------------------------------------- | | NPM | https://www.npmjs.com/package/@kurocado-studio/styleguide | | Repository | https://github.com/Kurocado-Studio/styleguide | | Releases | https://github.com/Kurocado-Studio/styleguide/releases |

Standardize TypeScript projects with scalable, sharable, and forkable configurations.

Why This Exists

It provides a single source of truth to hanfor formatting, linting, and commit conventions, enabling consistency across Kurocado projects, external contributor work, and client deliverables. It is designed to be forkable and extensible while remaining flexible enough for clients to fork, adapt, and publish their own versions under @your-org/client-name-styleguide.

Getting Started

Install the style guide

pnpm add @kurocado-studio/styleguide

Then follow the official setup guide to apply configurations.

Enable CI/CD pipeline

# .github/workflows/lint.yml
uses: kurocado-studio/devops/.github/workflows/lint.yml@main

Use Cases

  1. Internal Team Adoption Used by Kurocado Studio developers to enforce consistent engineering standards across all projects.

  2. External Contributor Alignment Freelancers and contractors follow the same rules without extensive onboarding.

  3. Client Collaboration Clients may fork and publish a custom style guide to align with their internal policies.

  4. Rapid Prototyping Spin up fully configured projects on CodeSandbox or similar environments without manual setup.

Roadmap

  • DangerJS integration
  • JavaScript to TypeScript migration helpers
  • Client-styleguide scaffolding CLI
  • Contributor documentation

Documentation

Full setup instructions are available at: https://kurocado-studio.github.io/styleguide

Acknowledgements

The Kurocado Studio Style Guide was inspired by the Vercel Style Guide, particularly their thoughtful approach to linting, formatting, and consistency in fullstack projects.