Eureka on the web
When you want the answer in the next five minutes.
The agent works the prompt against patents and technical literature, citing every source.
Run your analysis now →A 17-family dataset on classifying open-source license text with machine learning, led by a filer with 3 families.
30 published records collapse into 17 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 13 of 30 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.
This landscape tracks records matching a search for open-source license text handled by machine learning, text classification or classifier methods. The underlying search string requires the terms to co-occur in the title, abstract or claims, which keeps the pool narrow: 17 simple patent families and 30 published records in total, with no date limit applied.
17 families is a small pool. The figures below describe what this particular search returned, not the shape of a field or industry, treat this page as a starting point for a deeper search rather than a finished map.
Ordered by volume only, not by importance or claim strength. Counted in simple (DOCDB) patent families, so one invention filed in several countries counts once. Names come from Patsnap's standardised assignee field as recorded on each document; subsidiaries and group companies are not merged. The icon before each name is read from the name itself (words such as University, Institute or Ltd); the data carries no organisation-type field, so treat it as a reading aid rather than a classification. Filings held by named individuals rather than organisations are removed where they can be identified (4 here); that identification is not exhaustive, so an individually held filing can still appear below. Either way those filings stay inside the totals above. This table shows the top 11 of the 11 filers returned for this search; the data endpoint returns at most 100 entities, so even that 11 is not the complete set of filers. A single family can name more than one filer, so these counts overlap and do not add up to the total.
Two views of the same 17-family, 30-record dataset: when records were first filed, and which IPC subclasses they carry.
Records run from a single filing in 2012 up to 2 in 2026, with a peak of 9 in 2021. The years from 2022 onward are still filling in as later filings publish, so the recent downturn on the chart reflects publication lag rather than fewer filings.
Counted in published records by earliest filing year, not de-duplicated into families. A filing is counted in the year it was filed, but it only becomes visible after it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. 2022 onwards are therefore still filling in and are shaded; no growth figure on this page uses them. Because this series counts documents rather than inventions, a rise can mean more inventions or the same inventions filed in more countries; this dataset cannot separate the two.
G06F (electric digital data processing) appears on 13 of the 17 families (76.5%), G06N (computing based on AI models) on 10 (58.8%), and G06Q (business, commerce & admin data processing) on 3 (17.6%). A family can carry more than one of these classes, so the shares add up to more than 100%.
Shares are the percentage of the 17 patent families in scope. One patent family can carry several IPC classes, so the shares add up to more than 100%.
This page is one run against one query. Ask Eureka your own question about open source software license text classification using machine learning patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaA software package is received and unpacked into a plurality of components. Features are extracted from each component indicative of whether it presents a software supply chain risk, and one or more machine learning models consume those features to determine a risk level that can be provided to a consuming application or process. Component identities can also be identified using machine learning or other similarity analyses, in some cases using embeddings to characterize risk or provide component identities.US20250322336A1, BINARLY INC, filed 2025-10-16. Shown as the database's default first result, not as the most cited, newest or broadest record in scope.


Selected as the first record the search returns under the database default order, then shown in full. It is not ranked by citations, claim breadth or commercial importance, and it is not a judgement about which filing in this space matters most.
When you want the answer in the next five minutes.
The agent works the prompt against patents and technical literature, citing every source.
Run your analysis now →When it has to run inside your own pipeline.
Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.
Browse MCP servers →Three figures taken directly from the dataset, each counted in the unit stated.
AMAZON TECH INC is named on 3 of the 17 simple patent families in scope (17.6%). This is a single-row figure; filer rows are not rolled up to corporate group and cannot be added together, since one family can name several filers.
10 of the 11 listed filers hold 2 or fewer simple patent families each. Filings held by named individuals are excluded from this list but remain inside the 17-family and 30-record totals.
G06F (electric digital data processing) appears on 13 of 17 families and G06N (computing based on AI models) on 10 of 17. Since a family can carry both classes, these shares add up to more than 100% and are not mutually exclusive.
13 of the 30 published records (43%) were granted and still in force at the 2026-10-22 retrieval date. This is a legal-status snapshot at one point in time, not a measure of which filings are strongest.
Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to open source software license text classification using machine learning patent landscape, with the prior art for and against each one.
This page surfaces counts and classes; the follow-up work is reading claims and tracking specific filers.
A family count or an abstract cannot establish what a granted claim covers. Pull the claim sets for any record that matters to a specific product decision.
Explore full records in EurekaThe filer list here is a snapshot of volume, not of intent or strategy. Watching new filings from the same names over time gives a fuller picture than one count.
Set up filer tracking in EurekaA 17-family pool this small is sensitive to the exact terms used. Adjusting the search string can surface adjacent records this page's terms missed.
Refine this search in EurekaThis dataset returns 17 simple patent families and 30 published records matching a search for open-source license text handled by machine learning, text classification or classifier methods. No date limit was applied to the search, so this spans every matching record the search string could find regardless of filing date. Because the pool is small, it should be treated as a starting point for a deeper search rather than a complete count of everything filed in this space, since different wording in a search string can surface different records.
Among the 11 organisations returned by this search, AMAZON TECH INC holds the largest single-row share at 3 of 17 simple patent families (17.6%). 10 of the 11 listed filers hold 2 or fewer families each, which is a long tail rather than a concentrated field. These filer rows cannot be added together to produce a combined share, because one family can name more than one filer and the rows overlap; also note the list excludes filings held by named individuals, even though those remain in the overall totals.
The two largest IPC subclasses are G06F (electric digital data processing), appearing on 13 of 17 families (76.5%), and G06N (computing based on AI models), appearing on 10 of 17 (58.8%). G06Q (business, commerce and administration data processing) appears on 3 of 17 (17.6%). A family can carry more than one of these classes at once, so the percentages add up to more than 100% rather than partitioning the dataset.
The filing trend counts published records by earliest filing year, running from 1 record in 2012 up to a peak of 9 in 2021 and 2 in 2026. Records filed from 2022 onward are still publishing, so the drop visible in the most recent years reflects publication lag rather than an actual fall in filings. Reading a slowdown or any other trend out of the last few years of this chart is not supported by the data.
No. The filer list returned by this search is capped at the organisations it surfaces, excludes filings held by named individuals, and does not roll entries up to a corporate parent, so a company and its subsidiaries would appear as separate rows if both were present. It is also ordered purely by family count, which says nothing about claim scope, validity or commercial value. Treat it as a view into this specific search, not a ranking of ownership in the field.
No. This page reports family counts, IPC classes and one example abstract; none of these establish what a granted claim actually requires. Freedom-to-operate and infringement questions depend on reading the granted claims and prosecution history of the specific record in question, not on a count or an abstract summary. Anyone making a filing or design decision based on this topic should pull the full claim text for the relevant records first.
Go past this page: query the whole open source software license text classification using machine learning patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.
Search. Every figure on this page comes from one Patsnap search, run once and not edited afterwards. This is the exact search string:
TAC:(("open source" OR "open-source") AND license AND ("machine learning" OR "text classification" OR classifier))
Reading the field codes: TAC searches the title, abstract and claims of each record, not the full description. The search string sets no date limit, so the scope is every matching record in the database regardless of when it was filed. It is not restricted to recent years. How this string was built matters for how far the counts can be pushed. It was generated in batch from a topic list rather than hand-crafted for this page, and the result set is not manually screened. A keyword search over title, abstract and claims both over-captures (unrelated filings that happen to use the same words) and under-captures (the same invention written in different words). This page cannot measure either effect, so read every figure here as what this particular string returned, not as what exists in the field. One subclass (G06F) carries 76.5% of the patent families, so this search returned a classification-tight set.
What is being counted. Two different units appear on this page and they are not interchangeable. The filer list and the technology split are counted in simple (DOCDB) patent families: one invention counts once however many countries it was filed in. The total, the jurisdiction split and the filing-year chart are counted in published records: the same invention counts once per publication. For this search that is 30 records and 17 families. Record counts reward filing in many jurisdictions; family counts do not. Shares are only ever taken against a denominator in the same unit, and each one names it.
Who the filers are. Names come from Patsnap's standardised assignee field, as recorded on the documents themselves. They are not rolled up to corporate group: a parent and its subsidiaries appear as separate entries, and a portfolio acquired from another company stays under the name on the document unless the assignment is reflected there. This list is meant to carry organisations, not people. Filings held by a named individual are identified by matching the assignee against the inventors on the same search, and, for names written in Chinese, Japanese or Korean characters, by the name carrying no organisational suffix; those are removed from the list (4 of them here). Neither test is exhaustive: the inventor list it matches against is itself capped, and a personal name written in Latin script with no organisational wording in it cannot be told apart from a short company name by rule. So an individually held filing can still appear in the list. Those filings stay inside every total and share on this page either way, so the listed entries can add up to less than the total. A record shown in full further down still names its assignee exactly as the patent office records it, including where that is a person: that name is how the record is identified and checked. What is left out of the ranking is people as ranked entries, not people as cited sources. The table shows the top 11 of the 11 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 11 is not every filer. One patent family can name several filers and each is counted separately, so these rows are not slices of a divided whole: adding them together over-counts, and this page deliberately publishes no combined "top five" share for that reason. See every filer, individuals included
Dates. The year chart counts by earliest filing year, not publication year. A filing only becomes visible once it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. Measured across these pages, the year four back from today still holds only about 89% of its eventual count. 2022 onwards are therefore shaded on the chart as still filling in. The data behind this page was retrieved on 2026-10-22.
Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (13 of 30). Everything else is pending, withdrawn, refused, lapsed or not determinable, and those states are not broken out here because the underlying codes do not separate them cleanly. Legal status changes continuously and is reported per document, not per family. Get the status breakdown in Eureka
Classification. The technology split uses IPC subclasses (four characters, for example H01M). A single record usually carries several, so the shares add up to more than 100% and a record can appear in more than one bar. Subclass is a coarse grouping; it describes the field a record was classified into, not what the claims cover. Break the classes down to subgroup level
Who wrote the words. The tables, charts, counts, shares and patent numbers on this page are produced directly from the search result by a program; none of them are written or estimated by a language model. The surrounding prose, headings, FAQ answers and the answers in the question panel are drafted by a language model that is given those same figures and is not permitted to introduce others. Prose can still mis-describe a correct figure, so where the two disagree, the tables and charts are the record.
Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.
Patent data carries limitations that apply to every figure above. Recent filings are under-counted, because an application is not public until roughly 18 months after filing and database loading adds further delay. The search string defines and constrains everything shown: records that use different terminology, or that sit outside the fields searched, are absent and cannot be counted. Applicant names, classification codes, legal-status codes and citation records are taken as recorded and may contain errors, duplicates, omissions or stale entries. Ordering by volume is not a measure of quality, scope, enforceability or commercial value, and a larger portfolio is not a stronger one. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.
Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, validity or infringement search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. No attorney-client relationship is created by it. Any patent, commercial, or strategic decision should be verified independently against the primary records and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.
The question panel. The answers behind the suggested questions on this page were written when the page was generated, not in response to your click. The progress steps that play before an answer appears are an animation of how that analysis was done; nothing is being searched or computed at that moment. Typing your own question instead opens Patsnap Eureka, which does run it live.
Help us improve
Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.
This page