Skip to content
Back to the index

repo-tester

PyPIInfrastructure

PulseGate's liveness check found it on 13 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 30 Jun 2026. How this is checked

repo-tester is an open-source command-line tool that scans GitHub repositories for malicious code and supply chain security risks. It helps developers ensure the safety of their codebases by detecting potential threats before integration. Suitable for developers and security teams focused on code integrity.

Inferred · not functionally tested

Open SourceMITCLI
Visit PyPI

Overview

5 features

Purpose: Detecting and preventing malicious code and security risks in GitHub 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: cli

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, repo-tester takes a focused approach. Inferred · not functionally tested: It focuses on detecting and preventing malicious code and security risks in GitHub repositories. Inferred · not functionally tested: It is built as an open-source project for developers. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: repo-tester is available on the command line.

Dennis J. Carroll builds and maintains repo-tester, and it first shipped in 2026. Development happens publicly on GitHub with 36 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include repository scanning, malicious code detection, and supply chain security.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Repository scanning
  • Malicious code detection
  • Supply chain security
  • CLI interface
  • MIT license

Topics: Inferred · not functionally tested

Tags
repository-scannermalicious-code-detectionsupply-chain-security

JSON profile · Text profile · Access guide

Built with & integrations

Framework
FastAPI
Connectors
github
Runs on
CLI

Trust & compliance

License
MIT
Public signals
HTTPSOpen SourceFree tierGitHubActive maintenance

Indexing history

What PulseGate has recorded for this listing

Nothing recorded for this listing in this window.

Frequently asked questions about repo-tester

What does repo-tester do?
Inferred · not functionally tested: Repo-tester focuses on detecting and preventing malicious code and security risks in GitHub repositories. It is catalogued under Penetration testing & red teaming on PulseGate.
Who should use repo-tester?
Inferred · not functionally tested: repo-tester is an open-source project built for developers.
Does repo-tester have a free plan?
Basis unknown · not verified: Yes — repo-tester is open source under the MIT license and free to use.
What platforms does repo-tester run on?
Basis unknown · not verified: repo-tester runs on the command line.
Is repo-tester still active?
PulseGate's liveness check found it on 13 Sep 2026. Its GitHub repository shows 36 commits in the last 90 days.
What are alternatives to repo-tester?
Similar projects tracked by PulseGate include repo-proofer, repo-healthcheck, and repocheck-cli.repo-prooferrepo-healthcheckrepocheck-cli
Who develops repo-tester?
repo-tester is developed by Dennis J. Carroll.
When did repo-tester launch?
repo-tester first shipped in 2026.

Similar projects

Closest matches by what these projects do