r/TrueOpenSource • • 6d ago

Contribution: Developer Tools We built an open-source dependency security scanner with advisory-level reviews and audit trails – looking for feedback

Post image

Hey everyone!

Over the past month, our team has been working on an open-source project called AdvisoryTrail, and we've recently made it public.

The idea came from something we noticed while working with dependency security tools.

Most scanners identify vulnerable dependencies and report the findings. But identifying a vulnerability is only part of the problem. In a real development workflow, someone needs to review it, decide whether it is a false positive or an actual risk, document the reasoning, and be able to revisit that decision later.

We wanted to build something that focuses on that review and accountability process.

What does AdvisoryTrail do?

Here's what we've implemented so far:

- GitHub integration: Connect GitHub repositories and verify repository access before adding them, including private repositories.

- Dependency scanning: Uses Google's OSV-Scanner to identify known vulnerabilities in project dependencies.

- Advisory-level findings: Instead of grouping everything under one vulnerable package, we create a separate finding for each advisory. For example, we encountered a pinned version of `handlebars` with 20 associated advisories. Each advisory should have its own review decision.

- Baseline comparison: Distinguishes newly introduced vulnerabilities from pre-existing findings and resolved issues.

- Finding reviews: Reviewers can manage finding statuses and document why a decision was made.

- Audit trails: Records who performed an action, when it happened, and the associated reason.

- Policy enforcement: Supports Report Only, Warn on PR and Enforce Blocking Check Runs modes through GitHub integration.

Technology stack

- Backend: Python, FastAPI

- Frontend: React, TypeScript

- Database: PostgreSQL

- Dependency scanning: OSV-Scanner

- Deployment: Docker

AdvisoryTrail is self-hosted, so users run their own backend and manage their own deployment.

The project is released under the MIT licence. You can inspect the source code, run it locally, modify it or contribute to it.

What we're looking for

This is still an early-stage project, and we'd genuinely appreciate feedback from people who work with application security, DevSecOps or open-source security tooling.

A few things we'd particularly like feedback on:

  1. Does the advisory-level finding approach make sense, or would you prefer a different way of grouping vulnerabilities?

  2. What additional analysis should a dependency security platform provide beyond basic vulnerability detection?

  3. What features would make this useful in an actual development team's workflow?

  4. Are there architectural or security concerns we should address before expanding the project?

We're not claiming to have solved dependency security. We've built a first version around a problem we found interesting, and we'd like to learn from people who have experience in this space.

GitHub: https://github.com/Umang-sudo-su/advisorytrail

Contributions, issues, suggestions and constructive criticism are all welcome!

Thanks for reading!

0 Upvotes

1 comment sorted by

•

u/trueopensource-bot 🤖 Robot 6d ago

About this project · Umang-sudo-su/advisorytrail
⭐ 3 stars · 🍴 0 forks · 👥 6 contributors · 📄 MIT · 💻 Python
History: started Oct 2026 · last code change today · 102 commits on 14 different days in the last 90 days
Releases: none published yet
Open issues and pull requests: 0

Facts from GitHub when this was posted. I'm a bot.