secsentry
PulseGate's liveness check found it on 5 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 4 Sep 2026. How this is checked
secsentry is an open-source command-line scanner for detecting leaked secrets in Git working trees and repository history. It deduplicates findings at the blob level and creates masked case files, with support for security workflows such as pre-commit checks, SARIF, and GitHub Actions.
Inferred · not functionally tested
Overview
6 featuresPurpose: Detecting and investigating leaked credentials in Git repositories before they cause security incidents.
Inferred · not functionally tested
Audience: developers and security teams
Inferred · not functionally tested
Functions: data_extraction, monitoring
Inferred · not functionally tested
Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
In the Penetration testing & red teaming space, secsentry takes a focused approach. Inferred · not functionally tested: It focuses on detecting and investigating leaked credentials in Git repositories before they cause security incidents. Inferred · not functionally tested: secsentry is an open-source project aimed at developers and security teams. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: secsentry is available on the command line, and it can be self-hosted.
Behind secsentry is Umer Aamir, and it first shipped in 2026. Development happens publicly on GitHub with 12 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include working tree scanning, git history scanning, and secret detection.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Working tree scanning
- Git history scanning
- Secret detection
- Blob deduplication
- Masked case files
- Pre-commit support
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
Frequently asked questions about secsentry
- What is secsentry?
- Inferred · not functionally tested: Secsentry focuses on detecting and investigating leaked credentials in Git repositories before they cause security incidents. It is catalogued under Penetration testing & red teaming on PulseGate.
- Who should use secsentry?
- Inferred · not functionally tested: secsentry is an open-source project built for developers and security teams.
- Does secsentry have a free plan?
- Basis unknown · not verified: Yes — secsentry is open source under the MIT license and free to use.
- What platforms does secsentry run on?
- Basis unknown · not verified: secsentry runs on the command line. It can also be self-hosted.
- Is secsentry still maintained?
- PulseGate's liveness check found it on 5 Oct 2026. Its GitHub repository shows 12 commits in the last 90 days.
- Who makes secsentry?
- secsentry is developed by Umer Aamir.
- When did secsentry launch?
- secsentry first shipped in 2026.
- Is secsentry open source?
- Basis unknown · not verified: Yes — secsentry is open source under the MIT license, developed on GitHub.
Similar projects
Closest matches by what these projects do