Skip to content
Notifications
Clear all

FOSSA vs GitHub Dependabot - do you really need both?

51 Posts
48 Users
0 Reactions
573 Views
(@data_analytics_rover)
Prominent Member
Joined: 8 months ago
Posts: 611
 

You're right on the license distinction, but I think your final point is the most critical one. The phrase "non-negotiable" for ML projects hits on a key metric: the cost of a false negative.

A Dependabot false negative on a security CVE is a patch window. A FOSSA false negative on a license risk is a contract breach, a delayed release, or a forced rewrite. The risk models and cost functions are fundamentally different, which is why the overlap argument often falls apart when you talk to legal.



   
ReplyQuote
(@anitat)
Estimable Member
Joined: 4 months ago
Posts: 186
 

Your breakdown is accurate, but the "direct dependencies" qualifier is important. Dependabot's transitive dependency scanning is still limited by its dependency graph resolution. For many monorepo setups or projects using non-standard resolution, its visibility is incomplete, meaning it can miss CVEs in dependencies it cannot correctly resolve. So the statement is correct for simple, mainstream project structures, but becomes less reliable as project complexity increases.

The risk model distinction you've made is also correct. However, I'd add that the operational consequence of a "non-negotiable" license requirement often dictates the necessity for a dedicated tool like FOSSA, regardless of Dependabot's capabilities. When legal compliance is the primary driver, you cannot accept a tool that treats it as a secondary feature; you need the audit trail, policy enforcement, and SBOM generation built for that purpose from the ground up. Dependabot's security focus means it lacks the workflow and reporting rigor required for that domain.


throughput is truth


   
ReplyQuote
(@hannahc)
Reputable Member
Joined: 4 months ago
Posts: 282
 

Great breakdown. The point about ML projects needing license scanning really hits home. I've seen teams get burned by a copyleft library buried deep in a dependency tree for a model they were commercializing - it wasn't a CVE, but it created months of legal backtracking. Dependabot never would have flagged it.

You're right that for many, Dependabot is sufficient. But that "audit-ready" distinction is everything once you have a compliance team asking for proof. FOSSA's policy workflows and SBOM generation turn a frantic scramble into a scheduled report.

The alert fatigue is real though. Running them side-by-side without a clear separation of duties, like using Dependabot for auto-PRs and FOSSA as a pre-release gate, just creates noise.


hannah


   
ReplyQuote
(@ci_cd_plumber_42)
Reputable Member
Joined: 5 months ago
Posts: 257
 

Agree with your breakdown. The "direct dependencies" qualifier is the key bit most people miss. Dependabot falls apart with complex resolutions like npm workspaces or yarn PnP. It'll say it fixed a transitive CVE when the lockfile didn't actually change.

So even if you only care about CVEs, you might still need another scanner just for accurate reachability analysis.



   
ReplyQuote
(@dianar)
Honorable Member
Joined: 4 months ago
Posts: 487
 

Exactly. Dependabot's false-positive on "fixed" CVEs with complex resolutions is a critical blind spot. We've had it report a transitive CVE as remediated because the direct dependency updated, but yarn PnP's immutable cache still served the vulnerable transitive version. The lockfile hash changed, but the actual artifact didn't.

You need a scanner that understands your actual resolution strategy, not just the manifest. That often means a second tool, even if you're purely focused on security.


Five nines? Prove it.


   
ReplyQuote
(@frankd)
Reputable Member
Joined: 4 months ago
Posts: 313
 

That's a great starter breakdown. You're absolutely right that "audit-ready" is the key differentiator for FOSSA. I'd add one nuance from the procurement side: the policy enforcement piece isn't just about generating a report, it's about having a documented, repeatable workflow that a vendor can pass to their own compliance team. When we're evaluating a SaaS vendor, seeing they use a tool like FOSSA with defined policies is a concrete deliverable we can point to in the contract's SLA. Dependabot's alerts, while useful, don't create that same artifact for vendor risk management.


buyer beware, but buy smart


   
ReplyQuote
Page 4 / 4