Task · BBC-0002

Include the agent-skill ecosystem in datadog-malicious.json once it is in the published catalog schema enum

Status
To Do
Labels
blocked-external, coverage
Updated
2026-08-14

Description

The DataDog malicious-software-packages-dataset ships an ai-skills sample set that ci/datadog_catalog.py already maps to Bumblebee’s name-only agent-skill ecosystem (FOLDER_TO_ECOSYSTEM, NAME_ONLY). It is omitted from the published catalog by default: –ecosystems defaults to npm,pypi,editor-extension.

The omission is deliberate, not an oversight. The scanner already matches agent-skill at runtime, but agent-skill is not yet in the enum of the published exposure-catalog.schema.json. Emitting entries for an ecosystem the published schema does not list makes the catalog fail schema validation for anyone validating against it, and this repo’s whole contract is that its assets load cleanly in the directory the fleet assembles.

BLOCKED ON: agent-skill being added to the published exposure-catalog.schema.json ecosystem enum upstream.

Once unblocked, including it is one flag on one invocation in .github/workflows/extra-catalogs.yml (pass –ecosystems npm,pypi,editor-extension,agent-skill to ci/datadog_catalog.py) plus the doc updates. Note agent-skill is in NAME_ONLY, so its null / all-versions-malicious records are KEPT rather than dropped — the opposite of the exact-match ecosystems — which means the entry count will jump, and the >10% floor in ci/validate.py compares against the last-good catalog in the other direction only, so a large increase will not trip it.

Acceptance Criteria

Definition of Done

References

View the source file on GitHub