Skip to content
Notifications
Clear all

Switched to FOSSA from a homegrown script. The audit trail feature saved us during a vendor review.

1 Posts
1 Users
0 Reactions
0 Views
(@jamesk)
Estimable Member
Joined: 1 week ago
Posts: 80
Topic starter   [#8376]

Hey folks, been running FOSSA in our production pipeline for about six months now, after ditching a cobbled-together Python script that parsed `go.mod` and `package.json` files. The difference is night and day, especially for compliance.

Our old script basically spit out a list of licenses. That was fine for engineering, but it fell apart when legal and security needed a historical audit trail. Last month, a major vendor asked for a full third-party bill of materials and proof of our compliance checks over the last year. I almost panicked.

FOSSA’s audit trail feature was the absolute hero. It logs every scan, who triggered it, the policy decisions (allow/deny) for each license, and the exact snapshot of dependencies at that point in time. We could literally provide a timeline.

Here’s a snippet from the audit log API response we pulled for their request:
```json
{
"scan_id": "abc123",
"timestamp": "2024-01-15T08:30:00Z",
"initiator": "jenkins/prod-pipeline",
"project_revision": "main@a1b2c3d",
"policy_decisions": [
{
"dependency": "lodash@4.17.21",
"license": "MIT",
"action": "approved",
"rule": "auto-approved-oss-license"
}
]
}
```
Having this structured, machine-readable history meant we didn't have to dig through old CI logs or reconstruct past states.

Key takeaways from the switch:
* **The policy engine is central.** We defined rules for auto-approval (MIT, Apache-2.0) and flagging (AGPL, unknown). Every scan enforces this consistently.
* **The deep linking to specific builds** is a lifesaver. Our security team can click from a FOSSA finding directly to the Git commit and Jenkins build that introduced it.
* **Cost-wise,** it replaced about 40 hours a month of manual review and script maintenance. The ROI was clear for our platform team.

Biggest pitfall we hit early: not integrating it at the right stage. Initially we ran it only on PRs, but we missed dependencies pulled in during the actual build. Now it's in our final container build stage, scanning the final artifact.

If you're on the fence about moving from a homegrown solution, the auditability alone is worth it for any kind of vendor or regulatory compliance. Happy to share our Helm chart values for the FOSSA CI orb equivalent setup.

-jk



   
Quote