Key Takeaways
- TuxCare’s 2027 Open Source Landscape Survey is open through December 31, 2026, and takes about 12 minutes.
- Among last year’s respondents whose organizations reported an incident, 61.4% said an available patch hadn’t been applied.
- This year’s questions follow a package’s whole life, including AI-added dependencies, abandoned projects, and compliance evidence.
- For every 100 completed responses, TuxCare donates $500 to open source community initiatives, and finishers can enter a prize draw.
There’s a familiar kind of security problem. The vulnerability is known, a fix exists, and somebody already opened a ticket for it. The affected component is still running in production anyway, because the update needs testing, a change window, or changes to something else that depends on it.
Last year’s survey put a number on it. Among respondents whose organizations reported a cybersecurity incident, 61.4% said the incident happened while a patch was available but hadn’t been applied. The year before, it was 60.4%. And 92.6% of that same group said their organization knew it was vulnerable before the incident occurred.
Most of those teams knew about the hole. The fix just hadn’t made it to production yet.
That gap is what TuxCare’s 2027 Open Source Landscape Survey sets out to measure, along with a few newer problems. It’s open now through December 31, 2026, and takes about 12 minutes. There’s no product pitch, and we only publish combined results.
Take the 2027 Open Source Landscape Survey
Entering the prize draw? Jump down to the official giveaway rules.
What last year’s numbers actually told us
Among respondents who knew their organization’s incident status, 47.8% reported a cybersecurity incident in the previous 12 months. At organizations with 1,001 to 10,000 employees, that climbed to 64.2%. Bigger organizations have more surface area, and they may simply be better at spotting and reporting incidents – the survey can’t say which.
Confidence was thinner than most security teams would admit in a meeting. Fewer than one in four respondents (22.4%) said they were very confident that their open source components, transitive dependencies included, were up to date and secure. And 15.9% said they continue to use end-of-life components without updates.
Picture a hypothetical insurer running hundreds of Java services. Its scanner keeps flagging the same vulnerable libraries, but the fixes stay stuck behind testing and maintenance windows. Everyone on the team knows about them, and they’re still sitting in the backlog next quarter.
The full 2026 Open Source Landscape Report is a free download if you want the rest of the numbers before taking this year’s survey.
What happens after a package gets approved
A package can look perfectly fine on the day it enters the stack. Two years later, a vulnerability has been disclosed in one of its transitive dependencies, the original maintainer has moved on, and updating one library means checking half a dozen others first.
The survey follows that whole lifespan. It asks where your developers and build systems get their packages, what checks run before something new is adopted, and whether a malicious or typosquatted package has made it into any of your environments. It also asks how confident you are in the packages nobody on your team selected directly.
AI coding assistants and agents add a new wrinkle. Some can now add or update dependencies directly in your codebase, and it isn’t always obvious how those packages should be reviewed. A developer accepts a suggested fix at 4 p.m. on a Friday, the assistant pulls in a package nobody on the team has vetted, and it’s in production by Tuesday.
Then there’s end of life. Some projects announce it months ahead with a migration guide. Others just go quiet, and the application depending on that code may have years left to run. We’re asking how teams find out, what they do next, and how often they’ve needed a security fix for a package whose maintainers went silent without ever announcing an end of life.
The gap between knowing and fixing
Last year’s results pointed to a stubborn link between incidents and unapplied patches, so this year’s survey digs into the reasons. It asks whether patching critical or high-priority open source vulnerabilities has gotten faster or slower, what holds the process up, and whether your team is keeping up with the number of vulnerabilities it has to assess or falling behind.
It also asks how soon you expect a fixed version after a critical vulnerability is published. That one matters more than it sounds – a team that expects a fix within a day plans very differently from one with no set expectation at all.
Then come the questions on regulation and evidence. The survey asks which regulations and frameworks apply to your organization, and what customers, auditors, and regulators have asked your organization to provide, such as SBOMs, provenance attestations, proof of how quickly a vulnerability was fixed, and evidence of security support for end-of-life components. A team might have an SBOM somewhere, but producing a complete, current one on request is a different job, so the survey also asks how quickly your organization could produce one.
It finishes with ownership, meaning which teams handle the day-to-day work of open source security and whose budgets pay for the tools and services behind it. Those two answers don’t have to match, and when they don’t, that’s worth knowing.
If you’re on a platform or AppSec team, most of this will feel familiar. If you sit in compliance, the regulation and ownership questions are where your experience counts the most.
Who should take it
If you’re involved in or knowledgeable about how your organization manages its open source, this survey is for you. That covers developers and engineering leads, security and AppSec people, platform engineers and SREs, and the compliance folks who end up answering the auditor’s questions.
Maybe your team has a process that’s working unusually well. Maybe there’s a problem every tool claims to solve that still eats up your week. Both are worth hearing about.
If supply chain security isn’t your area, the survey checks before that section and skips its detailed questions. And if you aren’t involved in or knowledgeable about how your organization manages open source, the survey politely ends after the second question.
Several questions carry over from last year, so the 2027 report can show where practices have changed and where the same problems keep turning up.
The donation and the prize draw
For every 100 completed responses, TuxCare will donate $500 to open source community initiatives.
There’s also a prize draw. Complete the survey, then leave your email at the end to enter for a LEGO Stranger Things set, a Flipper Zero, or a $100 Amazon gift card (or regional equivalent). And yes, the Flipper Zero is there to make those 12 minutes a little more tempting. Your email is used only to run the draw, including contacting winners, and everything else is covered in the official giveaway rules below.
Add your perspective before December 31
The survey closes on December 31, 2026, and the prize draw follows in January 2027. After that, the results go into the 2027 Open Source Landscape Report, published on tuxcare.com in early 2027. Last year’s report was a free download with no form to fill out, and if your team takes part, your answers will be part of what this year’s report shows.
Twelve minutes is about the length of a standup that ran long. This one might actually be useful.
Take the 2027 Open Source Landscape Survey
Official giveaway rules
No purchase necessary. The 2027 Open Source Landscape Survey prize draw (the “Giveaway”) is run by TuxCare Inc. (“TuxCare”). No purchase or payment of any kind is needed to enter or win, and buying TuxCare products or services won’t improve your chances.
Entry period. Entries are accepted from the date the survey opens on November 16, 2026 until 11:59 p.m. Pacific Time on December 31, 2026.
Eligibility. The Giveaway is open to individuals who are at least 18 years old, or the age of majority where they live if that’s higher, and who live in a country where this kind of promotion isn’t prohibited by law. TuxCare employees and their immediate family members aren’t eligible. Entrants are responsible for making sure that taking part and accepting a prize is allowed under their employer’s policies, including any gift rules that apply to public sector employees.
How to enter. Complete the survey and enter your email address in the optional field at the end. Only completed surveys count, and each person may enter once. Incomplete, automated, duplicate, or fraudulent entries will be disqualified.
Prizes. Three prizes will be awarded, one per winner, in this order: a LEGO Stranger Things set (approximate retail value $300 USD), a Flipper Zero (approximate retail value $200 USD), and a $100 USD Amazon gift card or a regional equivalent of similar value. The total approximate retail value of all prizes is $600 USD. If a prize can’t legally be shipped to or used in a winner’s country, TuxCare may substitute a prize of similar or greater value. Prizes can’t be transferred or exchanged for cash, and winners are responsible for any taxes, duties, or import fees.
Winner selection and notification. In January 2027, TuxCare will randomly draw three winners from all eligible entries. The first winner drawn receives the first prize listed above, the second winner receives the second prize, and the third winner receives the third prize. Winners will be contacted at the email address they provided and must reply within 14 days, or an alternate winner may be drawn. The odds of winning depend on the number of eligible entries received.
How your email is used. The email address you provide is used only to run the Giveaway, including contacting winners, and it won’t be added to any marketing list. TuxCare’s privacy policies explain how personal data is handled.
Open Source Community donation. The donation to open source community initiatives is separate from the Giveaway and doesn’t depend on whether you enter the prize draw.
Social platforms. The Giveaway is in no way sponsored, endorsed, or administered by, or associated with, Facebook, Instagram, Meta, LinkedIn, X, or Mastodon. By entering, each entrant releases those platforms from any liability connected with the Giveaway.
General terms. TuxCare may cancel, suspend, or modify the Giveaway if fraud, technical problems, or other issues outside its control affect its fairness, to the extent permitted by law. The Giveaway is void where prohibited. Questions can be sent through TuxCare’s contact page.
