What's new in LibTracker

Website pages now have a /fr or /en address, and former addresses redirect to the French version. If you open a link in a language other than your browser's, a banner offers you the page in your language.

When you create a release, from the app or from your CI, LibTracker now checks your dependency files before starting the analysis and tells you exactly which file to add or remove. For Pipenv, Poetry, uv, Composer and Cargo, the manifest (Pipfile, pyproject.toml, composer.json, Cargo.toml) is now required alongside the lockfile: add it to the LibTracker step of your CI. A failed release no longer counts toward your monthly quota.

Buttons to add, edit or delete a release, a webhook or a CI key are hidden or disabled when your role does not allow it, and these actions are refused server-side for members without the matching right.

The changelog is now published on libtracker.io, along with a "Sources and method" page detailing where our data comes from and comparisons with Dependabot, Snyk and Dependency-Track.

Various stability and interface improvements.

Drop your dependency file and get, within moments, the number of vulnerabilities for each affected dependency, their severity and which ones are already exploited. Share the report with a link valid for 30 days that you can delete at any time, and browse examples from well-known projects to see what you'll get.

Every release gets a score out of 100 across five areas (security, remediation effort, freshness, maintenance, licenses), compared with the previous release: you can see at a glance whether your project is getting better.

Various stability and interface improvements.

When a prospect asks Google, ChatGPT or Claude which tool to pick, they now have everything they need to present LibTracker accurately: what the product does, who it's for, and at what price.

Full browser tab titles, an English version better recognized by browsers and search engines, and a FAQ that says plainly who LibTracker is for — and who it isn't.

This page is now visible without being signed in.

Choose your notification language (French or English), your Slack or Discord channel — recognized automatically — and the watch depth: the latest release, all of them, or a custom count.

Every alert now shows the affected project and release, the severity and a direct link to the vulnerability. Email subjects name the project and the CVE, so you can triage at a glance.

If a payment fails, your subscription shows "Payment past due" while retries run, with no loss of access.

A canceled subscription is no longer a dead end: the subscription form becomes available again, and a dedicated button keeps your invoice history within reach.

Unsure about your subscription state? The “Refresh status” button re-syncs the display with your billing in one click.

Assorted security, stability and interface improvements.

Your projects are now continuously re-scanned: a newly published vulnerability affecting one of your dependencies is detected and you get notified in under an hour.

Affected version ranges are interpreted more precisely: a vulnerability already fixed in the version you use no longer shows up by mistake in your reports.

Stability improvements and various fixes.

Get notified immediately when a vulnerability in your projects is being actively exploited. A key asset to prioritize your fixes and meet your reporting obligations (CRA, Article 14).

Clearer navigation through your notifications and a redesigned view of your SDK list.

Your reports are now more reliable: each vulnerability is matched to the right dependency, removing false positives from your projects.

Several pages have been redesigned with clearer information for a more readable experience.

Display fixes and various interface adjustments.

Analyze dependencies in your Flutter and Dart projects. LibTracker automatically detects vulnerabilities in your Pub packages, including indirect dependencies.

Missing SBOM reports on your older releases are now automatically generated on retry.

Use Claude, Cursor or any MCP-compatible AI assistant to query your LibTracker projects directly from your editor. One-click setup.

After a public scan, generate a share link to send the vulnerability report to your team or manager.

Drop your dependency file on the homepage and get a vulnerability report in seconds, no signup required.

The scanner now recognizes Gradle projects and simplifies ecosystem selection.

Understand the NIS2 directive requirements and how LibTracker helps you achieve compliance.

The pricing page displays remaining spots and the preferential Founder offer rate.

Discover LibTracker in 2 minutes with a demo video on the homepage.

Fixed broken links, improved pricing display and better cookie consent management.

Each dependency now clearly shows whether it's direct (in your code) or indirect (imported by another library).

A step-by-step guide to connect LibTracker to your deployment chain. Commands are generated for you.

The color coding for vulnerabilities and outdated versions is now unified for more intuitive reading.

Improved contextual help during setup and various visual fixes.

Get notified by email or webhook when a new vulnerability affects your projects. Choose your alert language.

Minor bug fixes and performance improvements across the platform.

Minor display fixes in your project list.

First release of LibTracker. Inventory your dependencies, detect known vulnerabilities, track your releases and automate your security audits.