
Security News
/Research
Popular node-ipc npm Package Infected with Credential Stealer
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.
devsecops-git-guardian
Advanced tools
π‘οΈ Block secrets, misconfigurations, and vulnerabilities before they reach your repository. Real-time security scanning with inline diagnostics.
Autonomous Security Enforcement for Git Workflows & CI/CD Pipelines
Block insecure code before it reaches your repository. A comprehensive security scanning tool that prevents secrets, misconfigurations, and vulnerabilities from entering your codebase. Available as a VS Code Extension, npm Package, and Docker Image for seamless integration into any development workflow.
π Multi-Scanner Security Engine
π‘οΈ Autonomous Enforcement
git push when violations foundπ Comprehensive Reporting
π§ Auto-Remediation
.gitignore filesChoose what you need:
# Install globally
npm install -g devsecops-git-guardian
# Or use without installation
npx devsecops-git-guardian
What you get:
Auto-setup:
.git folder existsCtrl+Shift+X)Or install from VS Code Marketplace
What you get:
Note: Extension works standalone OR with npm package for git hooks
docker pull vijaydevsecops/git-guardian:latest
docker run -v $(pwd):/workspace vijaydevsecops/git-guardian:latest
What you get:
| Use Case | Recommended Method |
|---|---|
| Node.js developer | npm package (CLI + hooks) |
| VS Code user | Extension only (or both!) |
| Want git protection | npm package (for hooks) |
| Want inline warnings | VS Code extension |
| CI/CD pipeline | npm package OR Docker |
| Full experience | npm package + VS Code extension |
π― Smart Auto-Setup (npm package only):
.git exists# Scan current directory
devsecops-scan
# Only critical issues
# Scan specific path
devsecops-scan /path/to/your/project
# Only show critical issues
devsecops-scan --severity CRITICAL
# Generate HTML report
devsecops-scan --format html --output security-report.html
# Auto-fix .gitignore security issues
devsecops-scan --fix
Ctrl+Shift+P) β DevSecOps: Scan Repository// @devsecops-ignore or @devsecops-ignore-file# Basic scan
docker run -v $(pwd):/workspace vijaydevsecops/git-guardian:latest
# With custom options
docker run -v $(pwd):/workspace vijaydevsecops/git-guardian:latest \
--severity MEDIUM --format json --output /workspace/report.json
name: Security Scan
on: [push, pull_request]
jobs:
security:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Security Scan
run: npx devsecops-scan --severity MEDIUM
security-scan:
image: vijaydevsecops/git-guardian:latest
script:
- scan $CI_PROJECT_DIR --severity MEDIUM
pipeline {
agent {
docker { image 'vijaydevsecops/git-guardian:latest' }
}
stages {
stage('Security') {
steps {
sh 'scan . --severity MEDIUM'
}
}
}
}
latest tag instead of pinned versionsOPTIONS:
-p, --path <path> Path to scan (default: current directory)
-s, --severity <level> Minimum severity (LOW|MEDIUM|HIGH|CRITICAL)
-f, --format <format> Output format (text|json|html|csv)
-o, --output <file> Save report to file
--no-block Don't exit with error code on violations
-v, --verbose Verbose output
--fix Auto-fix .gitignore security issues
-h, --help Show help
--version Show version
{
"devsecops.autoInstallHooks": true,
"devsecops.blockOnViolation": true,
"devsecops.severityThreshold": "medium",
"devsecops.scanExclusions": [
"node_modules/**",
"dist/**",
"build/**"
]
}
0 - No security violations found β
1 - Security violations found (blocks CI/CD) β2 - Scan error occurred β οΈβββββββββββββββββββββββββββββββββββββββββββ
β Security Scanner β
β (Orchestrator) β
ββββββββββββββ¬βββββββββββββββββββββββββββββ
β
ββββββββββΌβββββββββ
β β β
βΌ βΌ βΌ
ββββββββββ ββββββββββ ββββββββββ
βSecret β βDocker β βConfig β
βScanner β βScanner β βScanner β
ββββββ¬ββββ βββββ¬βββββ βββββ¬βββββ
β β β
βββββββββββΌβββββββββββ
βΌ
ββββββββββββββββββ
β Policy Engine β
β (BLOCK/ALLOW) β
ββββββββββ¬ββββββββ
βΌ
ββββββββββββββββββ
β Report β
β Generator β
ββββββββββββββββββ
For detailed information, see:
# Clone repository
git clone https://github.com/vijay-devsecops/git-guardian.git
cd git-guardian
# Install dependencies
npm install
# Build VS Code extension
npm run package
# Build CLI for npm
npm run build:cli
# Build everything
npm run build:all
# Test locally
npm test
Contributions are welcome! Please follow these steps:
git checkout -b feature/amazing-feature)git commit -m 'Add amazing feature')git push origin feature/amazing-feature)Please ensure your code:
MIT License - Free to use for personal and commercial projects.
If DevSecOps Git Guardian helped secure your codebase, please consider:
This tool is designed to find security vulnerabilities, but no tool is perfect. If you discover a security issue in DevSecOps Git Guardian itself, please email vijaypalsinghrathore575@gmail.com directly rather than opening a public issue.
Built with dedication for the DevSecOps community π‘οΈ
FAQs
π‘οΈ Block secrets, misconfigurations, and vulnerabilities before they reach your repository. Real-time security scanning with inline diagnostics.
The npm package devsecops-git-guardian receives a total of 3 weekly downloads. As such, devsecops-git-guardian popularity was classified as not popular.
We found that devsecops-git-guardian demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.Β It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
/Research
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.

Security News
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.

Security News
Packagist urges PHP projects to update Composer after a GitHub token format change exposed some GitHub Actions tokens in CI logs.