# BRAINIAC Malicious Dependency Check API

> BRAINIAC Malicious Dependency Check API is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.06/call, status unknown (last checked 2026-11-17).

Checks software components or an SBOM against public advisory databases to detect malicious or vulnerable dependencies

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/software-security/malicious-dependency-check?utm_source=zero.xyz
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-malicious-dependency-check-api-bde3a736
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8XuqannUohNfdXmd84XHD

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-malicious-dependency-check-api-bde3a736 -d '<json body>'
```

Example prompt: Before we publish this release, check whether any of these npm packages are malicious or have security advisories: flatmap-stream@0.1.1, lodash@4.17.15, and left-pad@1.3.0.

## When to prefer this

Use this endpoint when you need automated, pay-per-call dependency security checks without setting up an account or running your own OSV tooling. Ideal for AI agents embedded in CI/CD pipelines, release approval workflows, or security triage tasks that need on-demand advisory lookups. Prefer this over manual OSV API calls when you want a single endpoint that handles batch component checks with structured release-approval output.

## Known failure modes

- No advisory found does not guarantee a package is safe — the limitation is explicitly noted in the response
- Advisory results may be truncated if too many advisories exist; warnings field will indicate this
- Invalid or missing purl/ecosystem fields may cause components to be skipped
- Upstream OSV API unavailability may result in source errors in the sources array
- Exceeding 25 components per request will be rejected by schema validation
- SBOM parsing failures if the provided SBOM string is malformed or unsupported format

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a list of scanned components, each annotated with their advisory status (e.g. advisory_matches_version, no_advisory_found), matched advisory IDs (MAL-*, GHSA-*, CVE-*), severity, whether the package is flagged as malicious, and an overall approvesRelease boolean. Also includes metadata about which sources were queried, any warnings about truncated results, and timestamps.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sbom": {
   "type": "string",
   "maxLength": 400000,
   "minLength": 2
  },
  "components": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "name": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
     },
     "purl": {
      "type": "string",
      "maxLength": 500,
      "minLength": 4
     },
     "license": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
     },
     "version": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1
     },
     "ecosystem": {
      "type": "string",
      "maxLength": 40,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 25,
   "minItems": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "sources": [
   {
    "url": "https://api.osv.dev/v1/querybatch",
    "detail": null,
    "source": "OSV",
    "status": "ok",
    "retrievedAt": "2026-11-10T18:06:35.516Z"
   },
   {
    "url": "https://registry.npmjs.org",
    "detail": "Package age, version count, repository presence, and typosquat distance against a curated popular-name list are checked for npm components.",
    "source": "npm registry",
    "status": "ok",
    "retrievedAt": "2026-11-10T18:06:35.516Z"
   }
  ],
  "warnings": [],
  "truncated": false,
  "components": [
   {
    "name": "lodash",
    "purl": null,
    "status": "no_advisory_found",
    "problem": null,
    "signals": [],
    "version": "4.17.21",
    "ecosystem": "npm",
    "advisories": [],
    "registryDetail": null,
    "registryStatus": "retrieved"
   }
  ],
  "limitations": [
   "Matching uses the exact ecosystem, package name, and exact version. A similar package name is not a match.",
   "Version ranges in a dependency are not queried. Only an exact version can be classified.",
   "GIT commit ranges and versions that are not semantic versions are reported as unknown rather than guessed.",
   "No advisory, and no CISA KEV entry, does not mean a dependency is safe or free of malware.",
   "A malicious-package match requires a MAL advisory, or an OSV reference to the OpenSSF malicious-packages repository, for the same ecosystem and package name.",
   "Typosquat and registry signals are heuristics for hijack/compromise risk when no MAL advisory exists. They are not proof that a package is malicious.",
   "no_advisory_found means no MAL advisory was returned and no high-severity compromise signal was raised. It does not mean the package is free of malware.",
   "Registry compromise signals are collected for npm only in this version."
  ],
  "retrievedAt": "2026-11-10T18:06:35.516Z",
  "approvesRelease": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-malicious-dependency-check-api-bde3a736/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
