Sources
Every source the pages use, with its licence, the date we read its terms and what we take from it.
Every source the pages use, with its licence, the date we read its terms and what we take from it. Updated .
What we read
| Source | Licence or terms | Terms read | What we use |
|---|---|---|---|
| CISA Known Exploited Vulnerabilities catalog | CC0 1.0 Universal | 1 October 2026 | Every entry: CVE id, vendor, product, name, description, required action, listing and due dates, ransomware use, forensic triage, notes and links. Read hourly from CISA's own copy on GitHub (cisagov/kev-data, same licence), whose history since January 2025 gives our change log. |
| EPSS, the Exploit Prediction Scoring System (FIRST) | Free to use; FIRST asks for credit wherever the scores are shown | 1 October 2026 | The daily score and percentile of every CVE, and each day's file since 4 February 2022 for the lines on CVE pages and the score on the day CISA listed an entry. |
| CVE records (CVE Services, the CVE Program) | CVE Program Terms of Use | 2 October 2026 | The record of every listed CVE and of the CVEs EPSS rates 0.50 or more: description, dates, assigner, affected products and versions, CWE ids and CVSS. For the WordPress plugin and theme pages also the records of Wordfence, Patchstack and WPScan, the three CNAs that publish them: title, date, severity label and the affected products and versions. |
| CISA Vulnrichment | CC0 1.0 Universal | 2 October 2026 | CISA's SSVC decision points inside the CVE records: exploitation, automatable and technical impact. |
| CWE, the Common Weakness Enumeration (MITRE) | CWE Terms of Use | 2 October 2026 | The name of each weakness a CVE record or CISA's entry names. |
| Metasploit Framework module metadata (Rapid7) | BSD 3-Clause | 2 October 2026 | Facts only: which modules name a CVE, their name, type and rank. Never code, and never a path to it. |
| Exploit-DB repository index (OffSec) | GPL v2 for the repository | 2 October 2026 | Facts only, from the repository's index file: which entries name a CVE, their id, title, date and whether Exploit-DB verified them. Each entry is named by its Exploit-DB id; we read nothing from that site. |
| endoflife.date, product lifecycle dates | MIT License | 26 October 2026 | For each version of a software product: its release date, when support ends, when it reaches end of life, whether it is a long-term support version, and its newest release with that release's date. We use no product descriptions. |
| dotnet/core, release notes of the .NET runtime | MIT License | 27 October 2026 | For each release of the .NET runtime: its version, the day it came out and the CVE ids its release notes list. We take no download links, no hashes and no text of the notes. |
| GitHub Advisory Database, package advisories | CC BY 4.0 | 26 October 2026 | For each software package, its reviewed advisories: the id, the one-line summary, the severity label, the publication date, and the versions the advisory says are affected and the version it says fixes them. The records come from the OSV.dev export, which has no licence of its own, and only advisories of this database and the databases below are kept. We reword the version ranges as sentences and tables and make the dashes of a summary plain. Never the longer description of an advisory. |
| PyPA advisory database, package advisories | CC BY 4.0 | 26 October 2026 | The same facts for Python packages: the package, the affected and fixed versions and the advisory's id. Where GitHub's database has no record of an advisory, its one-line summary is the first sentence of PyPA's description. We reword the version ranges as sentences and never print the longer description. |
| Go vulnerability database, package advisories | CC BY 4.0 | 28 October 2026 | The same facts for Go modules: the module, the affected and fixed versions and the advisory's id. Where GitHub's database has no record of an advisory, its one-line summary is the Go database's own. We reword the version ranges as sentences and never print the longer description. |
| RustSec advisory database, package advisories | CC0 1.0 Universal | 26 October 2026 | The same facts for Rust crates: the crate, the affected and fixed versions and the advisory's id. Advisories whose text RustSec adapted from GitHub's database carry GitHub's licence, and then GitHub's database is credited too. |
| Erlang Ecosystem Foundation CNA, package advisories | CC BY 4.0 | 26 October 2026 | The same facts for Erlang and Elixir packages: the package, the affected and fixed versions and the advisory's id. We reword the version ranges as sentences and use no advisory text. |
| Drupal advisory database, package versions | MIT License | 26 October 2026 | Facts only: the package, the ids, the affected and fixed versions and the dates of its advisories. No advisory text and no severity, because the terms of the site that text comes from were not read. |
| FriendsOfPHP security advisories database | Public domain (The Unlicense) | 26 October 2026 | For each PHP package, the advisories GitHub's database does not have and the older lines of releases it does not list: the title, the CVE id when there is one, the affected versions of each branch and when each branch was fixed. Where GitHub's database holds the same advisory, the two are one row. We make the dashes of a title plain. |
The credit lines we use
- CISA Known Exploited Vulnerabilities catalog (CC0). Not affiliated with or endorsed by CISA.
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security.
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation.
- CWE names: Copyright © 2006-2026, The MITRE Corporation. CWE, CWSS, CWRAF, and the CWE logo are trademarks of The MITRE Corporation.
- Metasploit Framework module metadata: Copyright 2006-2026, Rapid7, Inc.
- Product lifecycle dates: endoflife.date, Copyright 2020 endoflife.date contributors (MIT License).
- Release notes of the .NET runtime: the dotnet/core repository, Copyright (c) .NET Foundation and Contributors (MIT License).
- Package advisories: the GitHub Advisory Database, the PyPA advisory database, the Go vulnerability database and the Erlang Ecosystem Foundation CNA (each CC BY 4.0), and the RustSec advisory database (CC0 1.0). Version ranges are reworded as sentences and tables, and the dashes of a summary are made plain.
- Package versions: the Drupal advisory database, Copyright 2025 Ackama (MIT License).
- FriendsOfPHP security advisories database (public domain).
The CVE Program's licence
The CVE Program Terms of Use say: "MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy."
- CVE Program Terms of Usecve.org
The CWE licence
The CWE Terms of Use say: "CWE is free to use by any organization or individual for any research, development, and/or commercial purposes, per these CWE Terms of Use. Accordingly, The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. Any copy you make for such purposes is authorized on the condition that you reproduce MITRE's copyright designation and this license in any such copy."
- CWE Terms of Usecwe.mitre.org
The endoflife.date licence
endoflife.date publishes its data under the MIT License. Its notice reads "Copyright 2020 endoflife.date contributors", and the licence goes on:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
- The MIT License of endoflife.dategithub.com
The dotnet/core licence
The dotnet/core repository is published under the MIT License. Its notice reads "Copyright (c) .NET Foundation and Contributors", and the licence goes on:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
- The MIT License of dotnet/coreraw.githubusercontent.com
The GitHub Advisory Database licence
GitHub's terms say: "The GitHub Advisory Database is licensed under the Creative Commons Attribution 4.0 license. The attribution term may be fulfilled by linking to the GitHub Advisory Database at https://github.com/advisories or to individual GitHub Advisory Database records used, prefixed by https://github.com/advisories." Every page that shows a package's advisories carries that credit in its closed Sources list.
- The GitHub Advisory Databasegithub.com
The Drupal advisory database licence
The Drupal advisory database is published under the MIT License. Its notice reads "Copyright (c) 2025 Ackama", and the licence goes on:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
We take facts from this database, never its text: package names, version ranges, ids and dates.
The FriendsOfPHP licence
The FriendsOfPHP security advisories database is released into the public domain. Its licence reads:
This is free and unencumbered software released into the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.
In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
- The licence of the FriendsOfPHP databasegithub.com
CISA's licence
CISA publishes its list under CC0 1.0 and says that using it "does not authorize you to use the CISA Logo or DHS Seal, nor should such use be interpreted as an endorsement by CISA or DHS." This site shows neither and claims no endorsement.
What we do not use
No vendor's advisory text: we link each advisory CISA names, but quote none. Microsoft's update guide is not a source here, because its terms allow only personal, non-commercial use; Microsoft's CVE records reach us through the CVE Program like every other.
The databases and programming interfaces of Wordfence, Patchstack and WPScan are not used: a WordPress plugin or theme page counts only what their CVE records say, and links none of their pages.
Of the package advisories we show GitHub's one-line summary (where GitHub has none, the first sentence of PyPA's description or the Go database's own summary) and FriendsOfPHP's title, never an advisory's longer description, and nothing of Drupal's text. A package page leaves out the reports of malicious code and the packages that only have such reports, because those advisories say to remove a package, not to upgrade it.