Datadog/security Signals

@webframp/datadog/security-signalsv2026.08.28.2· 13d agoMODELS

01README

Datadog Security Signals — signal search, triage, and archiving

02Release Notes

2026.08.28.2

Hardened codegen: instance names sanitized against path traversal; string schema patterns emit regex validation; output schemas passthrough unknown fields.

03Models1

@webframp/datadog/security-signalsv2026.08.28.2datadog/security_signals.ts

Global Arguments

Argument	Type	Required	Description
apiKey	string	yes	Datadog API key (DD-API-KEY)
appKey	string	yes	Datadog application key (DD-APPLICATION-KEY)
site	enum	yes	Datadog site

fn list_security_monitoring_signals(filter_query?: string, filter_from?: string, filter_to?: string, sort?: string)

Get a quick list of security signals

Argument	Type	Required	Description
filter_query?	string	no	The search query for security signals.
filter_from?	string	no	The minimum timestamp for requested security signals.
filter_to?	string	no	The maximum timestamp for requested security signals.
sort?	string	no	The order of the security signals in results.

fn bulk_edit_security_monitoring_signals_assignee()

Bulk update triage assignee of security signals

fn bulk_edit_security_monitoring_signals_state()

Bulk update triage state of security signals

fn bulk_edit_security_monitoring_signals()

Bulk update security signals

fn search_security_monitoring_signals(filter?: unknown, page?: unknown, sort?: unknown)

Get a list of security signals

Argument	Type	Required
filter?	unknown	no
page?	unknown	no
sort?	unknown	no

fn get_security_monitoring_signal(signal_id: string)

Get a signal's details

Argument	Type	Required	Description
signal_id	string	yes	The ID of the signal.

fn edit_security_monitoring_signal_assignee(signal_id: string, assignee: unknown, version?: unknown)

Modify the triage assignee of a security signal

Argument	Type	Required	Description
signal_id	string	yes	The ID of the signal.
assignee	unknown	yes
version?	unknown	no

fn edit_security_monitoring_signal_incidents(signal_id: string, incident_ids: unknown, version?: unknown)

Change the related incidents of a security signal

Argument	Type	Required	Description
signal_id	string	yes	The ID of the signal.
incident_ids	unknown	yes
version?	unknown	no

fn get_investigation_log_queries_matching_signal(signal_id: string)

Get investigation queries for a signal

Argument	Type	Required	Description
signal_id	string	yes	The ID of the signal.

fn edit_security_monitoring_signal_state(signal_id: string, archive_comment?: unknown, archive_reason?: unknown, state: unknown, version?: unknown)

Change the triage state of a security signal

Argument	Type	Required	Description
signal_id	string	yes	The ID of the signal.
archive_comment?	unknown	no
archive_reason?	unknown	no
state	unknown	yes
version?	unknown	no

fn get_suggested_actions_matching_signal(signal_id: string)

Get suggested actions for a signal

Argument	Type	Required	Description
signal_id	string	yes	The ID of the signal.

fn edit_security_monitoring_signal(signal_id: string, archive_comment?: unknown, archive_reason?: unknown, assignee?: unknown, state?: unknown, version?: unknown)

Update security signal triage state or assignee

Argument	Type	Required	Description
signal_id	string	yes	The ID of the signal.
archive_comment?	unknown	no
archive_reason?	unknown	no
assignee?	unknown	no
state?	unknown	no
version?	unknown	no

Resources

security_monitoring_signals(infinite)— Get a quick list of security signals

bulk_edit_security_monitoring_signals_assignee(infinite)— Bulk update triage assignee of security signals

bulk_edit_security_monitoring_signals_state(infinite)— Bulk update triage state of security signals

bulk_edit_security_monitoring_signals(infinite)— Bulk update security signals

search_security_monitoring_signals(infinite)— Get a list of security signals

security_monitoring_signal(infinite)— Get a signal's details

edit_security_monitoring_signal_assignee(infinite)— Modify the triage assignee of a security signal

edit_security_monitoring_signal_incidents(infinite)— Change the related incidents of a security signal

investigation_log_queries_matching_signal(infinite)— Get investigation queries for a signal

edit_security_monitoring_signal_state(infinite)— Change the triage state of a security signal

suggested_actions_matching_signal(infinite)— Get suggested actions for a signal

edit_security_monitoring_signal(infinite)— Update security signal triage state or assignee

04Previous Versions7

2026.08.28.1Aug 28, 2026

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.2

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.2Aug 27, 2026

2026.08.26.2

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.25.1Aug 26, 2026

2026.08.25.1

Changed: Updated labels for improved extension discoverability. Added cross-cutting category labels (security, observability, finops, infrastructure, networking, compliance, devops, ai, incident-response) where applicable.

updated labels

2026.08.24.1Aug 24, 2026

2026.08.24.1

Added: Output metadata attributes for observability.

durationMs: Method execution duration in milliseconds.
collectedBy: Extension name that produced the data.
fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).

2026.08.21.2Aug 22, 2026

2026.08.21.2

Changed: Error messages and input validation are more specific.

API errors now name the HTTP method and path that was attempted (e.g. Datadog API HTTP 404: GET /api/v2/security_monitoring/signals/abc-123) instead of just the raw status code and response body.
A network-level failure (DNS error, connection reset, timeout) reaching the Datadog API now raises Datadog API request failed: <METHOD> <path>: <reason> instead of an unlabeled fetch error.
signal_id is now rejected up front if empty on every method that takes it, instead of building a malformed request path.
edit_security_monitoring_signal_incidents now requires incident_ids to be a non-empty array of integers (it was previously typed as unknown and accepted anything, including nothing at all).

No changes to request/response shapes or existing successful-path behavior.

2026.08.21.1

Changed: Tightened and clarified Zod schemas as part of a repo-wide schema audit.

Added .min(1) to apiKey and appKey in the global arguments schema — both are sent directly as request headers, and an empty value would never be accepted by the Datadog API.
Added descriptions to previously undocumented filter, page, sort, assignee, incident_ids, version, archive_comment, archive_reason, and state arguments on the search and triage-edit methods, matching the wording already used for the equivalent resource schema fields.
Added a description to the result field on the bulk-edit resource schemas.

No behavioral changes — these are documentation and validation tightenings only.

2026.07.20.11

Added: Initial code-generated release of @webframp/datadog/security-signals with 12 methods covering the Datadog security signals API surface.

2026.08.21.1Aug 21, 2026

2026.08.21.1

Changed: Tightened and clarified Zod schemas as part of a repo-wide schema audit.

Added .min(1) to apiKey and appKey in the global arguments schema — both are sent directly as request headers, and an empty value would never be accepted by the Datadog API.
Added descriptions to previously undocumented filter, page, sort, assignee, incident_ids, version, archive_comment, archive_reason, and state arguments on the search and triage-edit methods, matching the wording already used for the equivalent resource schema fields.
Added a description to the result field on the bulk-edit resource schemas.

No behavioral changes — these are documentation and validation tightenings only.

2026.07.20.11

Added: Initial code-generated release of @webframp/datadog/security-signals with 12 methods covering the Datadog security signals API surface.

2026.07.20.11Jul 20, 2026

2026.07.20.11

Added: Initial code-generated release of @webframp/datadog/security-signals with 12 methods covering the Datadog security signals API surface.

05Stats

100 / 100

Downloads

Archive size

21.6 KB

Has README or module doc2/2earned
README has a code example1/1earned
README is substantive1/1earned
Most symbols documented1/1earned
No slow types (deprecated)1/1earned
Dependencies pass trust audit2/2earned
Has description1/1earned
Platform support declared (or universal)2/2earned
License declared1/1earned
Verified public repository2/2earned

Repository

https://github.com/webframp/swamp-extensions

06Platforms

linux · x86_64 linux · aarch64 macOS · x86_64 macOS · aarch64

07Labels

#datadog #security #signals #triage