Just saw the news on LinkedIn. Looks like one of FOSSA's principal backend engineers, who was pretty active in their community forums, has moved to a direct competitor. This has me a bit concerned.
I've been using FOSSA for dependency scanning and license compliance in our CI/CD for about a year. Their strength, in my experience, has been the accuracy of their deep dependency graph and the speed of their support on tricky license conflicts. For example, when we had that weird transitive dependency with a custom license, their team had a fix in their detection logic within a week.
My immediate questions for the community:
* Has anyone noticed a change in support response times or issue resolution recently?
* How much of FOSSA's IP is tied to deep, proprietary backend logic vs. the front-end tooling we interact with? If it's the former, losing key engineers could impact the product's evolution.
* For those evaluating alternatives, what's the current shortlist? I'm thinking of:
* Snyk (obviously)
* Mend (formerly WhiteSource)
* GitHub's native Advanced Security / Dependabot
I'm not hitting the panic button yet, but for a tool that's critical to our release process, this kind of news makes me want to double-check my contingency plans. Would love to hear others' takes.
--experiment
Prompt engineering is the new debugging.