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 🙏

© 2024 – Pkg Stats / Ryan Hefner

copyrights-action

v0.0.8

Published

A GitHub Action that checks the presence of copyright notices in all text files

Downloads

206

Readme

Check Copyrights in All Text Files

test License

This is a GitHub Action that checks the presence of copyright notices in all text files in the repository. Use it like this:

name: copyrights
on:
  push:
  pull_request:
jobs:
  copyrights:
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4
      - uses: yegor256/[email protected]

It will find the copyright punch line in the LICENSE.txt and then will try to find its presence in all source code files. If at least one of them doesn't have the punch line, the plugin will raise an error. A more fine-grained configuration is also possible:

- uses: yegor256/[email protected]
  with:
    license: LICENSE.txt
    globs: >-
      **/*.java
      **/*.py
      Makefile
      **/*.xml
    ignore: >-
      target/**
      node_modules/**/*.js

However, it is advised to stay with the defaults.

How to Contribute

If you want to contribute yourself, make a fork, then create a branch, then run npm test in the root directory. It should compile everything without errors. If not, submit an issue and wait. Otherwise, make your changes and then run npm test again. If the build is still clean, submit a pull request.