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

devops-practice

v1.2.0

Published

1. Create a new public GitHub repository "devops-practice" (or really whatever you like), or pick an old project of yours with no build automation nor CI. 2. If you created a new repo, write a program in a JVM-compatible language of your pick (Java, Groov

Vulnerabilities

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

Links

Maintainers

elenayanelenayan

Keywords

Readme

devops-practice

  1. Create a new public GitHub repository "devops-practice" (or really whatever you like), or pick an old project of yours with no build automation nor CI.
  2. If you created a new repo, write a program in a JVM-compatible language of your pick (Java, Groovy, Scala, Kotlin).
  3. Configure a build system to compile and run the program.
  4. Checkpoint: ask the teacher to take a look.
  5. Configure the git hooks to make sure that every commit message adheres to a convention (conventional commits are recommended).
  6. Configure a CI pipeline that compiles and executes the program on Linux.
  7. Create a build matrix for testing with multiple operating systems.
  8. Checkpoint: ask the teacher to take a look.
  9. Create an empty release job that runs only if the previous ones completed successfully.
  10. Configure the program for release on Maven Central. Use of dedicated plugins (e.g., https://github.com/DanySK/publish-on-central) is allowed.
  11. Make sure that you can upload and close the project on Maven Central.
  12. Make sure that you can upload and close the project on Maven Central automatically.
  13. Configure a new job, that runs in parallel with the ones that compile and test, which tests the upload and closure on central (dry-delivery).
  14. Make sure that the dry-delivery job runs only in case secrets are available (not on branch builds of forks, nor on pull request builds).
  15. Checkpoint: ask the teacher to take a look.
  16. Configure the branch protection on the default branch (whatever its name). No PR must be mergeable, unless the CI works, the branch is up to date, and there are no pending discussions.
  17. Configure semantic release to release on Central, following the commits convention you adopted.
  18. Make a first fully-automated release on Maven Central (if necessary, trick the bot by creating an empty commit with an appropriate message).
  19. Checkpoint: ask the teacher to take a look.
  20. Configure Renovate to propose updates via pull requests, auto-rebase-merging and auto-rebase-updating the PRs. If you have a centralized shareable configuration, you can reuse it.
  21. Checkpoint: ask the teacher to take a look.