📜 SPDX Software Licenses Scraper

🚀 Export the entire SPDX open-source license catalog in seconds. Pull 729 software licenses and 72 license-applicable exceptions with full legal text, OSI / FSF status, deprecation flags, and cross-references. No API key, no scraping rate limits, no manual list maintenance.

The SPDX Software Licenses Scraper exports the canonical SPDX License List, the open-source licensing standard adopted by GitHub, npm, Maven, PyPI, the Linux Foundation, and every major SBOM tool on the market. Each record contains the SPDX short identifier, the official license name, OSI approval status, FSF Free / Libre status, deprecation flag, the standard license template, and the full license body text.

The catalog covers MIT, Apache 2.0, GPL family, BSD family, MPL, EPL, Creative Commons, and every other recognized open-source license, plus license-applicable exceptions like Classpath, Bison, Autoconf, and GCC Runtime. Use it to bootstrap a license-compliance database, feed an SBOM generator, drive a legal review pipeline, or audit dependencies against a permitted-licenses allowlist.

🎯 Target Audience	💡 Primary Use Cases
Open-source compliance teams, legal counsel, SBOM tool builders, security engineers, package registry maintainers, DevSecOps platforms	License allowlist / denylist enforcement, SBOM enrichment, GPL / AGPL detection, OSI vs proprietary classification, full-text license diff and audit

📋 What the SPDX Software Licenses Scraper does

Three catalog modes in a single Actor:

• 📜 Licenses mode. All 729 SPDX-recognized open-source licenses with full text.
• ⚖️ Exceptions mode. All 72 license-applicable exceptions (Classpath, GCC Runtime, Autoconf, Bison, Font, etc.).
• 🔎 Single license mode. Pull one license by SPDX short ID for spot lookups.

Optional filters: OSI Approved only, FSF Free / Libre only, Include deprecated, and Include full license text for body-text export.

Each record includes the SPDX short identifier, official name, OSI / FSF flags, deprecation status, reference URL, see-also cross-references, and the full standard license template plus license body.

💡 Why it matters: the SPDX License List is the single source of truth for open-source license identification across SBOMs, package registries, and compliance workflows. Building your own scraper means tracking semantic-version bumps of the canonical list, parsing dual JSON layers, and stitching detail bodies back to the index. This Actor skips all of that.

📊 Data fields

Each record includes: detailsUrl, isDeprecatedLicenseId, isFsfLibre, isOsiApproved, kind, licenseId, licenseText, listVersion, name, referenceUrl, scrapedAt, seeAlso, standardLicenseTemplate. These field names come straight from the actor's dataset schema, so what you see here is what lands in your dataset.

🚀 How to use

1. 📝 Sign up. Create a free account with $5 credit (takes 2 minutes).
2. 🌐 Open the Actor. Go to the SPDX Software Licenses Scraper page on the Apify Store.
3. 🎯 Set input. Pick a mode (licenses / exceptions / single), apply optional OSI / FSF filters, and set maxItems.
4. 🚀 Run it. Click Start and let the Actor collect your data.
5. 📥 Download. Grab your results in the Dataset tab as CSV, Excel, JSON, or XML.

⏱️ Total time from signup to downloaded dataset: 3-5 minutes. No coding required.

🔗 Recommended Actors

• 📦 PyPI Package Scraper - Python package metadata for SBOM enrichment
• 📦 npm Package Scraper - JavaScript registry data and dependency trees
• 🐙 GitHub Repos Scraper - Repository metadata including license info
• 🔐 CVE Vulnerabilities Scraper - Security vulnerability database for risk scoring
• 🌐 OSV Vulnerability Scraper - Open-source vulnerability database

💡 Pro Tip: browse the complete ParseForge collection for more developer-data scrapers.

⚠️ Disclaimer: this Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the SPDX project, the Linux Foundation, the OSI, or the FSF. All trademarks mentioned are the property of their respective owners. Only publicly available open license data is collected.

🆘 Need Help?

If you hit a bug, have questions about setup, or need a scraper we haven't built yet, open our contact form or write to parseforge@protonmail.com. We also take on paid custom data projects.

For faster answers, join our Discord. It's the best place to get support and suggest new actors.