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

dependency-drift-tracker

v0.3.1

Published

Track your dependency drift across multiple repositories using libyear.

Downloads

31

Readme

Dependency drift tracker

Track your NPM dependencies drift across multiple git repositories using libyear. It store the result on flat files and display the drift over time via a webpage.

Usage

Using the GitHub Action

The dependency-drift-tracker GitHub action is the easiest way to use track your dependencies drift over time. It runs every day and update the data files. To get started, head over to the dependency-drift-status repository and click on Use this template button on the top right corner. Then enter a repository name and click on Create repository.

The next step is to enable GitHub Pages for your repository:

  1. Go to your repository Settings page
  2. Go to the Pages sub-section on the left
  3. Under Source, select Deploy from a branch
  4. In the Branch dropdown, select gh-pages and / (root)
  5. Click on Save

And then you edit the repositories.txt file to add the git repositories you want to to track, one per line. See the configuration section for more details on it.

Once finished, you can trigger an initial run of the action:

  1. Go to your repository Actions page
  2. Click on Update libyear info on the left
  3. In the message banner This workflow has a workflow_dispatch event trigger., click on Run workflow and in the dropdown click on "Run workflow" with the branch main.
  4. After a few minutes, your data files should be up to date

Standalone

The standalone version is not tied to GitHub action and do not require a git repository to store the data files.

Create an empty directory with a data directory.

mkdir --parents repository-drift/data
cd repository-drift

And create a repositories.txt file with one git repository per line. See the configuration option to learn more on it.

Then run:

npx dependency-drift-tracker

It will create or update json files in the data directory. You can then initialize a git repositories to keep track of the changes.

Configuration

The repositories.txt file contains the git repositories you want to track. Put one repository per line with the full URL to access it.

https://github.com/Dependency-Drift-Tracker/dependency-drift-tracker
https://github.com/Dependency-Drift-Tracker/dependency-drift-tracker-action

If your package.json is in a subdirectory, you can use the # to specify the path:

https://github.com/Dependency-Drift-Tracker/dependency-drift-tracker-action#path/to/dir

Private repositories

It's possible to clone private repositories or to hide parts of the repository using environments variables. For example with an environment variable named ACCESS_TOKEN, the following repository line could be updated https://[email protected]/Dependency-Drift-Tracker/dependency-drift-tracker-action.

Development

Run tests

npm test

License

GNU GPL 3