# Dev Ecosystem Report | npm PyPI crates GitHub OSV (`andok/dev-ecosystem-mcp`) Actor

Agent-ready package health reports for npm, PyPI, and crates.io packages plus GitHub repos: downloads, maintainers, repo health, and OSV vulnerabilities in one JSON row. $0.005/report + $0.02 start.

- **URL**: https://apify.com/andok/dev-ecosystem-mcp.md
- **Developed by:** [Andok](https://apify.com/andok) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 package reports

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Dev Ecosystem Report | npm, PyPI, crates.io, GitHub and OSV

Get an agent-ready **package health report** for any npm, PyPI, or crates.io package, or any public GitHub repository, in a single JSON row. Each report combines registry metadata, download counts, maintainers, GitHub repository health, and known vulnerabilities from the OSV.dev database, plus a simple `healthy / caution / risky` verdict with human-readable reasons.

Use it for dependency due diligence, supply-chain reviews, open-source vendor vetting, and as a tool call for AI coding agents that must decide whether a library is safe and maintained before adding it to a project.

### What each report contains

- **Registry data:** latest version, package description (`package_description`), license, homepage, repository URL, maintainers, first and last publish dates, version count, deprecated or yanked flag.
- **Downloads:** last day, last week, and last month for npm and PyPI; recent and total downloads for crates.io.
- **GitHub repo health:** stars, forks, open issues, language, license, archived flag, last push date, days since last push, latest release tag, and topics.
- **Vulnerabilities:** every OSV advisory affecting the latest published version, with ID, aliases (CVE), summary, severity, fixed-in versions, and a link.
- **Health verdict:** `level` plus `reasons`, for example "single maintainer (bus factor 1)", "GitHub repository is archived", or "known high severity vulnerabilities".

### Input

```json
{
  "packages": [
    { "ecosystem": "npm", "name": "express" },
    { "ecosystem": "pypi", "name": "requests" },
    { "ecosystem": "crates", "name": "serde" }
  ],
  "githubRepos": ["apify/crawlee"],
  "includeVulnerabilities": true,
  "includeGithubHealth": true
}
```

| Field | Description |
|---|---|
| `packages` | List of `{ ecosystem, name }`. Ecosystems: `npm`, `pypi`, `crates`. Scoped npm names are supported. |
| `githubRepos` | Standalone repos as `owner/repo` or a github.com URL. |
| `includeVulnerabilities` | Query OSV.dev. Default on. |
| `includeGithubHealth` | Fetch GitHub stats for each package's repository. Default on. |
| `githubToken` | Optional token to raise the GitHub limit from 60 to 5,000 requests per hour. |
| `concurrency` | Parallel packages, 1 to 10. |

### Pricing

Pay-per-event pricing:

- **Actor start:** $0.02 once per run.
- **Package report:** $0.005 per package or repository report generated.

Cost examples: 10 packages cost $0.02 + 10 × $0.005 = **$0.07**. 100 packages cost **$0.52**. 1,000 packages cost **$5.02**, or about $5 per 1,000 reports. Packages that do not exist and other failed lookups are returned with an `error` field and are **not charged**.

### Data sources

All data comes from public, documented APIs: the npm registry and download API, the PyPI JSON API and pypistats.org, the crates.io API, the GitHub REST API, and OSV.dev. No scraping and no logins.

### Tips

- For large batches, pass a `githubToken` so GitHub health lookups are not rate limited. Without it, repo health is skipped gracefully once the limit is hit and the rest of the report is still returned.
- PyPI download counts come from pypistats.org, which may rate-limit bursts; counts are returned as `null` when unavailable.
- Vulnerabilities are matched against the **latest version** of each package. Use the `fixed_in` field to see which versions patch each advisory.

### Use with AI agents

Output is a flat, typed JSON object per package, designed to be consumed by LLM tool calls through the Apify API or the MCP server for Apify Actors. Branch on `health.level` or `vulnerability_count` to approve or block a dependency automatically.

# Actor input Schema

## `packages` (type: `array`):

Packages to report on. Each item needs ecosystem (npm, pypi, or crates) and name. Scoped npm names like @scope/pkg are supported.

## `githubRepos` (type: `array`):

Standalone GitHub repositories as owner/repo or full github.com URLs.

## `includeVulnerabilities` (type: `boolean`):

Query OSV.dev for known vulnerabilities affecting the latest version.

## `includeGithubHealth` (type: `boolean`):

Look up stars, forks, open issues, last push, and archive status for the package's GitHub repository.

## `githubToken` (type: `string`):

Personal access token to raise the GitHub API limit from 60 to 5,000 requests per hour. No scopes needed for public repos.

## `concurrency` (type: `integer`):

Number of packages processed in parallel.

## `timeoutSeconds` (type: `integer`):

HTTP timeout per request.

## Actor input object example

```json
{
  "packages": [
    {
      "ecosystem": "npm",
      "name": "express"
    },
    {
      "ecosystem": "pypi",
      "name": "requests"
    },
    {
      "ecosystem": "crates",
      "name": "serde"
    }
  ],
  "githubRepos": [],
  "includeVulnerabilities": true,
  "includeGithubHealth": true,
  "concurrency": 4,
  "timeoutSeconds": 20
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `resultsCsv` (type: `string`):

No description

## `run` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "packages": [
        {
            "ecosystem": "npm",
            "name": "express"
        },
        {
            "ecosystem": "pypi",
            "name": "requests"
        },
        {
            "ecosystem": "crates",
            "name": "serde"
        }
    ],
    "githubRepos": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("andok/dev-ecosystem-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "packages": [
        {
            "ecosystem": "npm",
            "name": "express",
        },
        {
            "ecosystem": "pypi",
            "name": "requests",
        },
        {
            "ecosystem": "crates",
            "name": "serde",
        },
    ],
    "githubRepos": [],
}

# Run the Actor and wait for it to finish
run = client.actor("andok/dev-ecosystem-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "packages": [
    {
      "ecosystem": "npm",
      "name": "express"
    },
    {
      "ecosystem": "pypi",
      "name": "requests"
    },
    {
      "ecosystem": "crates",
      "name": "serde"
    }
  ],
  "githubRepos": []
}' |
apify call andok/dev-ecosystem-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,andok/dev-ecosystem-mcp"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xgkPDW6GDIUhHZ9wV/builds/6EhLTtgK2gS1r9GIM/openapi.json