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

@flyinmuyen/n8n-nodes-cipp-auth-token

v0.1.2

Published

n8n community node: get Microsoft 365 access tokens via certificate-based client assertion (SAM app / CIPP)

Readme

n8n-nodes-cipp-auth-token

An n8n community node that obtains Microsoft 365 OAuth access tokens using certificate-based client assertion (Secure Application Model / CIPP).

Installation

cd ~/.n8n/custom
npm install n8n-nodes-cipp-auth-token

Setup

  1. Create a credential of type CIPP SAM App API with:
    • Client ID — Azure AD Application (client) ID
    • Private Key — RSA private key in PEM format
    • Certificate — X.509 certificate in PEM format
  2. Add the CIPP Auth Token node to a workflow
  3. Set the Tenant ID to the target Azure AD tenant GUID
  4. Execute — the node returns the full OAuth token response

How It Works

The node implements the OAuth 2.0 client credentials flow with a signed JWT client assertion (RFC 7523):

  1. Computes the certificate's SHA-1 thumbprint (x5t) for the JWT kid header
  2. Builds and signs an RS256 JWT with the private key
  3. POSTs the assertion to https://login.microsoftonline.com/{tenantId}/oauth2/v2.0/token
  4. Returns the access token response for downstream use

Development

npm install
npm test       # run 18 unit tests
npm run build  # compile TypeScript to dist/

License

MIT