
OSS Audit (package due diligence)
io.github.santex85Published by GitHub account santex85v0.1.0Updated Nov 19, 2026
Open-source package due diligence: licences, release health, Scorecard, dependents, OSV vulns.
The publisher's own server: audit.domains - Domain Valuation
Overview
Lets an assistant vet open-source packages across npm, PyPI, Go, Maven, Cargo and NuGet for licences, release health, Scorecard and known vulnerabilities.
- What you can do
- Report on one package version: licence and copyleft category, latest version, release recency, dependents, repo stats, OpenSSF Scorecard and OSV vulnerabilities
- Build a licence table with copyleft flags and category counts for up to 50 packages
- List OSV advisories for a package or exact version, merged by alias, sorted by severity, with fixed versions
- Compare up to 10 alternative packages in one ecosystem side by side, with the best package per metric
- When to use it
- Useful before adopting a dependency, during licence review, or in technical due diligence when you want a quick, sourced picture of a package's licence, maintenance activity and known vulnerabilities.
- Requirements
- Runs as a local process; the README describes a Python virtual environment with pip requirements, started via stdio or streamable HTTP. No API key is needed. It needs network access to the deps.dev and OSV.dev APIs. Optional environment variables HOST, PORT and MCP_TRANSPORT control the transport.
Installation
In SourceWeft
- Open OSS Audit (package due diligence) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
OSS Audit MCP server (open-source package due diligence)
An MCP server that lets AI agents vet open-source dependencies before adoption, in a licence review, or during technical due diligence. For npm, PyPI, Go, Maven, Cargo (crates.io) and NuGet it reports licences with copyleft classification, release recency, dependents count, the linked repository's OpenSSF Scorecard, and known vulnerabilities with severity and fixed versions. It reads deps.dev and OSV.dev live and needs no API key.
Not legal advice and not a full security audit. Licence data is detected from package metadata and can be incomplete or wrong (e.g.
non-standard). A clean vulnerability result only means OSV has no advisory, not that the code is safe.
Tools
Example calls
Package naming: npm express, @types/node; PyPI requests (case-insensitive); Go module path
github.com/gin-gonic/gin; Maven groupId:artifactId; Cargo serde; NuGet Newtonsoft.Json. The ecosystem accepts
aliases such as python, rust, crates.io, golang and dotnet.
Licence categories
permissive · weak-copyleft (LGPL, MPL, EPL, CDDL, …) · strong-copyleft (GPL, EUPL, OSL, CC-BY-SA, …) ·
network-copyleft (AGPL, SSPL) · other/proprietary (LicenseRef, BUSL, Elastic, CC-BY-NC) · unknown.
An A OR B expression takes the least restrictive option and sets permissiveAlternative when a copyleft option is
also offered. A AND B takes the most restrictive. copyleftFamilies lists GPL/AGPL/LGPL/MPL/EPL hits explicitly.
Licence exceptions (WITH Classpath-exception-2.0) are not weighed, so review those by hand.
Severity
The GitHub advisory rating is used where OSV has one (MODERATE is shown as MEDIUM). Otherwise the server computes
the CVSS v3.x base score from the vector. CVSS v4-only advisories without a rating show UNKNOWN. Advisories that
alias each other (GHSA / PYSEC / CVE / GO / RUSTSEC) are merged into one entry, which keeps the GHSA record and lists
the others in alsoKnownAs.
Limits and data caveats
- "Latest version" is the registry default. When that default is a pre-release (e.g.
1.0.0.dev6), the newest stable release is used instead.latestReleaseAtis the newest publish of any version, including pre-releases. Go pseudo-versions (untagged commits) are excluded from version counts. - Dependents come from deps.dev's v3alpha
:dependentsendpoint. It can change, and it returns 0 or nothing for some ecosystems/packages (e.g. Cargoserdeshows 0; Go and NuGet return none). A note is added when the count is 0. - Repository, stars and Scorecard depend on deps.dev linking a source repo. Older versions often lack the link, so the latest version's link is used as a fallback. Scorecard results are weekly snapshots.
vulnerabilitieswithout a version follows up to 3 OSV result pages.truncatedUpstreamis set if more exist.- Caps: 50 packages per
check_licensescall, 10 percompare_packagescall, 100 advisories returned, 6 concurrent upstream requests, 30 s HTTP timeout, 120 s per tool call, 12 MB per upstream response.
Data sources and attribution
- deps.dev API v3 (Open Source Insights, Google),
https://api.deps.dev. Its generated data is licensed CC-BY 4.0, so every response carries anattributionfield. Keep it when you redistribute results. Attribution: "Package, licence, dependents and Scorecard data from deps.dev (Open Source Insights by Google), licensed CC-BY 4.0." - OSV.dev API v1,
https://api.osv.dev. Advisory records are aggregated from upstream databases (GitHub Advisory Database, PyPA, Go, RustSec, …) under those sources' own licences. I did not check OSV's terms during this build. Check them before commercial use. - The User-Agent is
oss-audit-mcp/0.1 (+MCP server; ...).
Run
Environment variables: HOST (default 0.0.0.0), PORT (default 8080), MCP_TRANSPORT (streamable-http, stdio or sse; default streamable-http). No API key is needed.
mcpize.yaml describes the build and start commands for MCPize.
Use with Claude Desktop or another MCP client
Local (stdio). Clone the repo, create the venv as above, then add this to claude_desktop_config.json
(or your client's MCP config), with the paths changed to where you cloned it:
Remote (streamable HTTP). Run .venv/bin/python src/server.py on a server and point any client that supports
remote MCP servers at http://<host>:8080/mcp. GET /health returns {"status": "healthy"}.
License
MIT, see LICENSE. The data returned by the tools stays under the terms of its sources (see above).
Source: README.md at commit 6ea47df
Tools
0Version history
1- v0.1.0LatestNov 19, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Audit integrations
audit.domains - Domain Valuation
domains.auditOfficial publisher
Deterministic domain-name valuation: fair-value intervals, comparable recorded sales, availability checks, and a verified for-sale listing market.
Revenue Agent — OpenAPI Audit & Change Detection
news.prhOfficial publisher
A remote MCP endpoint that audits OpenAPI specifications and detects API changes, charging $0.10 USDC per analysis via x402 on Base.
SEO Technical Audit
Published by GitHub account theharrisontruong-web
Remote MCP server that audits a single web page's technical SEO — indexing, meta tags, robots.txt, sitemap and schema — returning a score and grade.
Security Headers + TLS Audit
Published by GitHub account theharrisontruong-web
Remote MCP server that audits any website's security headers and TLS configuration, returning a 0–100 score, A–F grade and top gaps.
MailAuth Audit (Email Deliverability)
Published by GitHub account theharrisontruong-web
Audits a domain's SPF, DKIM, DMARC and MX records over DNS-over-HTTPS and returns a 0-100 score, A-F grade and spoofing/deliverability risk.