PAGES

0 of 12 breaking-change claims checked since 24 Sept · 0 corrections · Claim history

← all tools
◆ Secrets Detection & Management

Secretlint

v14.0.0 open-source

Free plan: not checked yet · Open source: yes

Secretlint is a pluggable linting tool to prevent committing credentials.

What you can do now

Checking Plays…

Summary

Secretlint is an open-source, pluggable linting tool that scans a codebase for committed credentials and secrets before they reach a repository, aimed at application developers and DevSecOps teams who want to catch leaked API keys and tokens at the source. It is free to use and runs locally as a CLI via Docker or npx, making it a one-command addition to a pre-commitpre-commitAn open-source framework for managing and running git hooks, maintained by the pre-commit project, that lets cyber tools enforce checks automatically on every commit before code reaches a repository. hook or CI pipeline. Its rule set is pluggable, shipping a recommended preset that covers credentials for services including AWS, GitHub, GitLab, Stripe, Cloudflare, HashiCorp Vault and Hugging Face, with output available as SARIFSARIFStatic Analysis Results Interchange Format, a standard for sharing code-analysis findings, including locations and rule details. It lets scanners report results to a common review interface. for code-scanning dashboards. The project sits in the secret-scanning space rather than in runtime monitoring. With 125 releases tracked and a release posted this week, it is actively maintained.

Secretlint is a pluggable linting tool to prevent committing credentials.

How Secretlint helps

Does my codebase contain any committed API keys or tokens before I push?

scans every file in the project against a built-in set of credential patterns for services including AWS, GitHub, GitLab, Stripe, Cloudflare, HashiCorp Vault, and Hugging Face, then reports each finding by file and rule, with an exit code of zero only when nothing is found

Which specific service's credentials were exposed in a given file?

each reported finding names the rule that matched — such as the GitHub App token rule or the Stripe API key rule — so the reader knows which service's secret is at risk, not just that something looked suspicious

Will my pre-commit hook catch a secret if I accidentally stage it?

integrates directly into a pre-commit hook and evaluates staged content before a commit is recorded, stopping the push at the point where the credential first appears rather than after it has entered history

Does the content I'm about to pipe into a process contain a secret?

accepts input through standard input and lints it against the same rule set, so content that never touches disk can still be checked before it is used

Are there credential strings scattered across files that my version control is already ignoring?

can be directed to scan files that fall inside gitignore patterns, covering build artefacts, local config files, and generated outputs that the normal commit path would never inspect

Where exactly in my codebase should I go to remove or rotate a detected secret?

reports each finding with the file path and the matched rule's description of why the pattern is considered a credential, giving enough location and context to act without guessing

all 13 features, with the evidence for each →

Languages

Not documented

Features

13 capabilities

Built from Secretlint's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Secretlint covers 1 of the 2 secrets and credential hygiene capabilities we track.

What Secretlint offers you

  • Command-line interface3
  • User-defined detection rules2
  • CI/CD pipeline integration1

All capabilities 13 capabilities
Secret and credential scanning Scans code and files for hardcoded secrets and credentials using configurable rules, reporting findings in multiple formats. 53 releases · 21 other sources · first seen Feb 2020

Shared capability: Secret scanning

Also counts toward: User-defined detection rules

Built-in detection rules for third-party services Ships detection rules covering credentials for a wide range of third-party services including GitHub, GitLab, Cloudflare, Stripe, Tailscale, Figma, Notion, Groq, Databricks, Vercel, Grafana, HashiCorp Vault, and Hugging Face. 15 releases · first seen Apr 2022
Node.js 12+ runtime requirement Requires Node.js version 12 or higher to execute. 5 releases · first seen Sep 2021
Multiple distribution platforms Executes the cyber tooling via npm package manager, Docker containers, and CLI quick-start packages. 4 releases · 1 other source · first seen Mar 2020

Also counts toward: Command-line interface

Gitignore-aware file traversal Respects .gitignore patterns by default when walking the file tree, with an option to scan ignored files explicitly. 2 releases · 2 other sources · first seen May 2026
In-place secret masking Rewrites a file in place, replacing detected secrets with masked values. 1 release · 3 other sources · first seen Jan 2023
STDIN linting Lints content piped via STDIN, enabling integration into shell pipelines and editor workflows. 1 release · 2 other sources · first seen Mar 2020

Also counts toward: CI/CD pipeline integration, Command-line interface

False-positive suppression Reduces noise by ignoring known-safe values such as example credentials in database connection strings and overly broad cryptographic key patterns. 2 releases · first seen May 2026
ESM rule definition support Supports loading secret detection rules via ECMAScript modules using named exports. 2 releases · first seen Sep 2021
Internationalization support Allows localization of output and messages through a locale configuration option. 2 releases · first seen Mar 2020

Also counts toward: Command-line interface

Configuration validation reporting Reports configuration problems as warning messages rather than silently failing when loading the config. 1 release · first seen Oct 2026
Pattern-based custom rules Allows users to define custom secret-detection patterns, with per-pattern allow-list configuration to suppress known false positives. 1 release · first seen Apr 2026

Also counts toward: User-defined detection rules

Structured table output Displays lint results in a structured table format for easier review. 1 other source · first seen Jun 2021

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Screenshots

From the release notes, newest first. Click one to see it full size.

v14.0.0 Nov 15, 2026

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Secretlint, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Secretlint puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

40 entries

  1. November 20261
  2. May 20261
  3. April 20263
  4. March 20261
  5. January 20261
  6. August 20253
  7. July 20251
  8. June 20251
  9. February 20252
  10. October 20244
  11. December 20231
  12. November 20232
  13. July 20231
  14. February 20231
  15. January 20231
  16. October 20221
  17. April 20222
  18. March 20221
  19. September 20211
  20. July 20211
  21. June 20212
  22. June 20201
  23. April 20202
  24. March 20204
  25. February 20201
    Show

    40 entries

    Project health

    Issue, contributor and maintainer activity in secretlint/secretlint, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 32% of issues opened, last 12 months
    5. Median time to close 12 days first maintainer reply 2.7 hours
    6. Open backlog 31 of 218 issues ever filed
    1. Issues opened / month 2 · 0 communitymaintainers
    2. Open backlog 31
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • bugs 8%
    • features 8%
    • other 84%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.