Skip to security report content

Open source security reports

Found a tool on GitHub?
Check it before you install it.

See what the Plexicus security scan flagged in popular open source projects, from leaked secrets to risky code, and what still needs a closer look. Free, no sign-up.

Find a project How to check any repo

We show what a scan found and what it did not check. No scan can promise that a project is safe.

Projects listed
39
With scan results
39
Queued for scanning
0

How it works

Three steps before you install

  1. Look up the project

    Search by project name or owner.

  2. See what the scan flagged

    Alerts by type and severity from the latest Plexicus scan.

  3. Decide how to use it

    Practical next steps, plus what the scan did not cover.

Security reports

Look up a project

Projects with scan results are listed first.

Stars show popularity, not security. Scan results may include alerts from earlier scans of the same repository.

Not on the list?

Scan any GitHub repository yourself with the free Plexicus SAST tool.

Scan a repository free

Checklist

How to check if a GitHub repo is safe to use

Stars tell you a project is popular, not that it is safe. Run through these checks before you install anything from GitHub.

  1. Check who maintains it

    Look for active maintainers, recent commits, and quick replies to issues. An abandoned project will not get security fixes.

  2. Read the issues and security advisories

    The Issues and Security tabs show reported vulnerabilities and how fast they were fixed.

  3. Look for leaked secrets

    API keys or passwords committed to the code are a red flag for how the whole project handles security.

    Covered in Plexicus reports

  4. Scan the code for risky patterns

    Static analysis finds injection, unsafe file access, weak cryptography, and similar issues before you run anything.

    Covered in Plexicus reports

  5. Check its dependencies

    Look for known-vulnerable packages and look-alike names (typosquats) in the dependency list.

  6. Limit the permissions you grant

    AI agents and MCP servers often ask for your files, shell, email, or tokens. Grant only what the task needs.

  7. Try it in isolation first

    Run new tools in a container or virtual machine with throwaway credentials, and pin a specific release.

FAQ

Questions about open source security

How do I know if a GitHub repository is safe to use?

No single check proves it. Look at who maintains it, read its issues and advisories, scan the code for secrets and risky patterns, and try it in isolation first. Plexicus reports cover the scanning part for popular projects.

Does a popular repo with many stars mean it is safe?

No. Stars measure popularity. Popular projects can still contain leaked secrets, vulnerable code, or risky default settings.

What does a Plexicus security report show?

Each report shows the automated alerts from Plexicus scans, grouped by type, such as secrets or code security, and by severity, plus which checks ran. Alerts are leads to review, not confirmed vulnerabilities.

Does zero alerts mean a project is safe?

No. It means the checks that ran found nothing to flag. Areas the scan did not cover, and code added later, can change the picture.

I maintain a listed project. How do I correct a report?

Open your project's report and use the correction link to send the relevant commit or evidence of a fix. Plexicus reviews the request and can arrange a new scan.

Can you scan a repository that is not listed?

Yes. Use the free Plexicus SAST tool to scan any GitHub repository you have access to.

Your own code

Scan your repository
for free.

Connect GitHub and see what Plexicus flags in your own code.

Scan your repository free
Qualification

Check whether AI Swarm Pentest fits your environment.

Share the minimum context. We will review the scope and tell you the next commercial step.

Before submitting — verify you fit

0 / 280

No commitment. If you don't fit, we'll tell you.
SAMPLE HANDOVER · ILLUSTRATIVE

Sample evidence handover

A trimmed view of what your team receives at the end of an AI Swarm Pentest engagement. Real engagements include full technical evidence, executive narrative, and a remediation plan.

VALIDATED FINDING Evidence attached

Server-Side Request Forgery in webhooks/receiver

demo-project/sample-app · src/webhooks/receiver.py:42

SeverityHigh CVSS 3.18.6 Priority79 Confirmedvia replay

Untrusted caller-supplied URLs reach an internal egress without an allowlist. Replayed in a sandbox against a fresh authorized target — the same control was validated to fail twice.

REVIEWER-READY REMEDIATION Merge-ready PR

Validate the target URL against an allowlist of permitted hostnames. Reject private/internal IP ranges. Enforce HTTPS only.

plexicus/remediation/webhooks-ssrf 3 changed · 0 new files
42resp = requests.get(target_url)
42+if not is_allowed_host(target_url):
43+  raise WebhookRejected(target_url)
44+resp = requests.get(target_url, timeout=5)
Every engagement hands over:
  • Executive briefing
  • Validated findings list
  • Merge-ready PRs
  • Compliance mapping (NIS2 · DORA · CRA)
 Private Round For investors