📦 deps.dev Package Insights Scraper

🚀 Pull open source package intelligence in seconds. Resolve the default version, licenses, security advisories, dependency graph, and publish date for any npm, PyPI, Cargo, Maven, Go, or NuGet package using Google's deps.dev API.

The deps.dev Package Insights Scraper turns Google's Open Source Insights data into a clean, structured feed of package facts. Give it an ecosystem and a list of package names, and it returns the resolved default version, the full version count, license identifiers, known security advisory keys, the resolved dependency graph, and the original publish time for each package, plus one row per resolved dependency.

It covers the npm (Node.js), PyPI (Python), Cargo (Rust), Maven (Java), Go (modules), and NuGet (.NET) ecosystems. All data comes straight from the public deps.dev v3 API, the same data that powers the deps.dev website, with no API key and no scraping of rendered pages.

🎯 Target Audience	💡 Primary Use Cases
Security and platform engineers	Auditing licenses and known advisories across a dependency list
Open source maintainers	Tracking version counts and publish cadence of packages
Data and supply chain teams	Building software bill of materials and dependency inventories
Developer tooling builders	Enriching package pages, dashboards, and internal catalogs

📋 What the deps.dev Package Insights Scraper does

• Looks up one or more packages in a chosen ecosystem (npm, PyPI, Cargo, Maven, Go, NuGet).
• Resolves the default or latest version flagged by deps.dev.
• Reports the total number of published versions for each package.
• Returns SPDX license identifiers for the default version.
• Lists known security advisory keys from OSV when the default version is affected.
• Resolves the dependency graph and counts the resolved dependencies.
• Emits one row per resolved dependency with its name, version, and relation.
• Captures the homepage and source repository links and the original publish time.

📊 Data fields

Each record includes: advisoryCount, defaultVersion, dependencyCount, licenses, name, publishedAt, results, scrapedAt, system, url, versionCount. 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. Create a free Apify account using this sign-up link.
2. Open the deps.dev Package Insights Scraper in the Apify Console.
3. Choose an ecosystem under system and add package names under packages.
4. Set maxItems if you want to cap the number of rows, then click Start.
5. Download the results once the run finishes, or pull them from the dataset API.

🔗 Recommended Actors

• npm Registry Scraper — package metadata straight from the npm registry.
• PyPI Packages Scraper — Python package details from PyPI.
• crates.io Rust Scraper — Rust crate metadata and stats.
• Maven Central Scraper — Java artifact data from Maven Central.
• Libraries.io Scraper — cross ecosystem package intelligence.

💡 Pro Tip: browse the complete ParseForge collection.

⚠️ Disclaimer: independent tool, not affiliated with Google or deps.dev. Only publicly available 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.