Dependency tracking · free for 3 projects
Know when your dependencies move
Inlinr reads the package.json of your repositories and keeps one feed of what their npm packages publish: releases with their notes, deprecations and security advisories. Dozens of releases a day, and you only read the few that need you.
Advisories reach you
An email when a critical or high advisory affects a project you follow, with the version that fixes it on your release line.
Only what matters
Majors, breaking notes and advisories stay on top. A day's patches, dev tooling's minors and @types bumps fold into one line.
Upgrades checked first
Before you bump: the peer ranges it breaks, Node and ESM-only changes, and the release notes in between, majors first.
Where you read
A private Atom feed per list of packages, an email for the packages you follow by name, and the same answers for an assistant through the Inlinr MCP server.
From a repository to a feed
1
Add a repository
Sign in with GitHub and pick one of your public repositories, or paste the address of any public one.
2
Inlinr reads its package.json
Every manifest of the default branch, workspaces included. The declared ranges only, never a lockfile's whole tree.
3
Private ones stay on your machine
For a private repository the CLI sends the manifests itself. Inlinr never asks GitHub for access to your private code.
Free to use without an account
- Package pages
Every release with its notes, advisories by release line, signals and alternatives.
- package.json check
Paste one: what is outdated, deprecated or affected by an advisory.
- Public API
Releases, upgrade notes and a check endpoint, as JSON.
Follow your first project
Free for 3 projects, Pro for every one. No extension to install: the feed fills as soon as a repository is added.