git-safe-publish
PulseGate's liveness check found it on 14 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 26 Jun 2026. How this is checked
git-safe-publish is an open-source command-line toolchain that helps developers detect and prevent the accidental publication of sensitive data through git. It integrates with git workflows to scan for secrets and enforce security best practices before code is published.
Inferred · not functionally tested
Overview
5 featuresPurpose: Preventing accidental exposure of sensitive data in git repositories.
Inferred · not functionally tested
Audience: developers
Inferred · not functionally tested
Functions: Unknown
Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: unknown
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: browser, cli
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
git-safe-publish sits in PulseGate's Password & secrets management category. Inferred · not functionally tested: It focuses on preventing accidental exposure of sensitive data in git repositories. Inferred · not functionally tested: git-safe-publish is an open-source project aimed at developers. Basis unknown · not verified: git-safe-publish is open source under the MIT license. Basis unknown · not verified: It runs on the web and the command line.
It is developed by Jason Berto, and it first shipped in 2026. The project is developed in the open on GitHub with 28 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include secret scanning, pre-commit checks, and sensitive data detection.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Secret scanning
- Pre-commit checks
- Sensitive data detection
- Git integration
- Command-line interface
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
What PulseGate has recorded for this listing
Frequently asked questions about git-safe-publish
- What is git-safe-publish?
- Inferred · not functionally tested: Git-safe-publish focuses on preventing accidental exposure of sensitive data in git repositories. It is catalogued under Password & secrets management on PulseGate.
- Who should use git-safe-publish?
- Inferred · not functionally tested: git-safe-publish is an open-source project built for developers.
- Does git-safe-publish have a free plan?
- Basis unknown · not verified: Yes — git-safe-publish is open source under the MIT license and free to use.
- What platforms does git-safe-publish run on?
- Basis unknown · not verified: git-safe-publish runs on the web and the command line.
- Is git-safe-publish still maintained?
- PulseGate's liveness check found it on 14 Oct 2026. Its GitHub repository shows 28 commits in the last 90 days.
- Who develops git-safe-publish?
- git-safe-publish is developed by Jason Berto.
- When did git-safe-publish launch?
- git-safe-publish first shipped in 2026.
- Is git-safe-publish open source?
- Basis unknown · not verified: Yes — git-safe-publish is open source under the MIT license, developed on GitHub.
Similar projects
Closest matches by what these projects do