contact_depscope
Submit tickets for bugs, new package/ecosystem listings, security disclosures, output anomalies with evidence, or partnership requests. Returns ticket or anomaly ID for tracking.
Instructions
Inbound ticket: bug/listing/security/anomaly/partnership. USE WHEN: reporting wrong data (bug), requesting a new pkg/ecosystem index (listing), disclosing a DepScope security issue (security), flagging a concrete mismatch in another tool's output vs. authoritative source (anomaly — provide tool_called+observed+expected), or partnership/press (partnership). RETURNS: {ticket_id} or {anomaly_id}.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Ticket category. `anomaly` routes to structured anomaly triage (requires tool_called/observed/expected). | |
| No | Reply-to email of the requester (required for bug/listing/security/partnership). | ||
| subject | No | Short subject line (3-200 chars). | |
| body | No | Message body (10-8000 chars). Be specific: include package name, ecosystem, error trace, repro steps when applicable. | |
| name | No | Sender display name (optional). | |
| company | No | Company / organization (optional). | |
| tool_called | No | For kind=anomaly: DepScope tool that produced the anomaly (e.g. check_package, get_migration_path). | |
| ecosystem | No | For kind=anomaly: ecosystem of the involved package, if any. | |
| package | No | For kind=anomaly: package name involved, if any. | |
| version | No | For kind=anomaly: package version involved, if any. | |
| observed | No | For kind=anomaly: what DepScope returned (1-1500 chars). | |
| expected | No | For kind=anomaly: what you expected to see (1-1500 chars). Be concrete. | |
| evidence_url | No | For kind=anomaly: URL to authoritative source (registry page, GHSA, CVE, repo, ...) supporting your expectation. |