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

@financial-times/next-secrets

v1.1.0

Published

This is like AWS's [git-secrets](https://github.com/awslabs/git-secrets) but better.

Downloads

16

Readme

next-secrets

This is like AWS's git-secrets but better.

npm install --save-dev @financial-times/next-secrets pre-git

Ensure the following is in package.json:

  "config": {
    "pre-git": {
      "pre-commit": [
        "node_modules/.bin/next-secrets"
      ]
    }
  }

That's it. From this point on, you can't commit any code that breaks the rules.

$ git commit
running bin/pre-commit.js script
executing task "next-secrets"

server/search.js:5:fetch(url, { headers: { x-api-key: 'a69c65f3-0db7...' } })

DENIED FILES

.env

DENIED STRINGS

file: server/search.js
line number: 5 
full line: fetch(url, { headers: { x-api-key: 'a69c65f3-0db7...' } })
deny match: a69c65f3-0db7...
deny rule: [a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12}

*** WARNING!!!! ***


Resolve the above.  For any potential secrets found, remove them from the code, whitelist them in project\'s secrets.js (strings only), or by tweaking the rules https://github.com/Financial-Times/next-secrets/blob/master/rules.js (strings and files)

Please see also https://github.com/Financial-Times/next-secrets/blob/master/SOLUTIONS.md for possible solutions

We are removing the files from the commit if added

Any problems, please contact the Next Platform team (#ft-next-platform)

*******************

pre-commit You've failed to pass all the hooks.

You cannot. Facepalm.

Teddy bear doing a facepalm

What code's not allowed?

The rules say what's allowed and what's not. See also the tests. Want changes? Please consult the Next Platform team.

Solutions to common issues

Please see here for ideas. This has the added bonus that it usually improves code's quality and security. Win-win. :-)