Black Duck buys Koders

Black Duck buys Koders

Summary: Black Duck Software has acquired Koders, the open source code search engine.


American Black Duck, from birdchasers birdchaser.blogspot.comBlack Duck Software has acquired Koders, the open source code search engine.

(A Black Duck spokesman says a picture of a hungry black duck would work well here. Rob Fergus of Birdchasers says black ducks like this little guy are threatened.)

Those looking at questions of profit should know that the press statement says Black Duck "acquired the assets of Koders." That's usually code for they didn't take the whole business, or its debts.

A statement in the release from Koders CEO Darren Rush seems to confirm this. “Black Duck is the ideal company to take over the Koders technology and our developer community,” he said.

In addition to maintaining the Koders Web site, Black Duck said it will incorporate its search technology into the rest of its portfolio.

In his statement, Black Duck CEO Doug Levin says Koders' code search will integrate well with Black Duck's existing component and fragment/file search capabilities.

Black Duck Software is a code management company, able to distinguish code under various licenses so companies stay in compliance with their licenses.

The last time I looked at merger activity in this space, back in October, I asked whether things were getting a bit frothy. This deal indicates the froth has been blown away.

Topics: Open Source, Software

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Koders Instead of Krugle?

    Personally, I like Krugle better than Koders. But it will be interesting to see how BDS integrates the Koders enterprise product with protexIP and exportIP.

    Also, it makes me wonder if Krugle will have to merge with Palamida...
    • Two fine questions

      You ask two good questions.

      I suspect the answer to the first (Koders or Krugle) is that Koders was a good deal.

      The second question, does this force Krugle to tie-up with someone else, is very intriguing. I'd like to get an answer to that, but I don't think it's a question that a Krugle executive can answer honestly.

      Their answer would doubtless be "no" until the moment they sign a contract and make the answer "yes."

      Sort of like the Atlanta Falcons denying they were going to take a quarterback with their first pick yesterday -- until they did.
      • More Questions

        Some more questions:

        1. Who's going to buy Ohloh? Their business plan seems to be that they get bought by someone eventually (they can't be paying the bills with ads).

        2. Who's going to take Ohloh to the next level? Give me more information about a project so I can make better decisions about what project to use. For example: there are a bunch of open source XML parsers out there, where can I find a centralized database (for lack of a better word) that allows me to compare them to chose the best one for my situation? Or SNMP library? Or report generation tool? etc.

        Useful information would include:
        - Licensing is of course very important. I may want a license that I can use with a GPL project or, conversely, I may want to exclude GPL or any other license that requires that the code be made public.
        - What standards does a project support, and to what level? (This is very difficult to do because it can't be reliably, widely automated, but it's very useful information)
        - Ohloh gives a line count which is somewhat useful, but how about other metrics such as McCabe's cyclometric complexity, which can help predict bugs in the code.
        - Results of static code analysis. I continue to be amazed at how many Java projects obviously don't take advantage of FindBugs to, well, find bugs. This isn't just no name projects you've never heard of, but widely used projects like those from Apache.
        - Code coverage: how completely do the tests of a project (assuming it has tests) tests the code. (again something that's hard to do). Perhaps let the project publish the numbers in a well-defined format and have the scanning software pick up that information.
        - Vulnerabilities: How many CVEs and Bugtraqs has a project had, when were they and what version were they? Hardly definitive, but useful input nonetheless.

        Come on Black Duck, Palamida, Ohloh, etc. give us this! ;-)
      • RE: Black Duck buys Koders

        A statement in the release from Koders <a href="">642-241 exam</a> CEO Darren Rush seems to confirm this. ???Black Duck is the ideal company to take over the Koders technology and our developer community,??? he said. In addition to maintaining the Koders Web site, Black Duck said it <a href=" ">JN0-343 exam</a> will incorporate its search technology into the <a href="">642-072 exam</a> rest of its portfolio.