Formats and running it
SIEM integrations and email
Your SOC should see a malicious package the moment ForgeRepo™ does, without anybody forwarding an email.
Integrations sends events to a generic webhook, Splunk HEC, or syslog over UDP, TCP or TLS as JSON or CEF. Each integration picks the events it wants: requested, cached, blocked, quarantined, approved, released, integrity changed, vulnerability discovered and remediated, malware detected, policy violation, waiver created and expired.
Every event carries the package, version, file hash, user, token name, application, environment, source address, policy, reason, CVE, CVSS, EPSS and CISA KEV. Passwords, token values and keys never are. Events are queued and delivered by a worker with retries backing off to an hour, so a SIEM that is down never slows an install.
A webhook with a secret signs each request with an HMAC over the timestamp and body, so a receiver can reject replays. Addresses on the box itself and cloud metadata addresses are refused, rechecked on every send, and redirects are never followed.
Email goes out through SMTP or Microsoft 365 Graph, as an hourly digest at most, only to somebody with something new to hear.
In short
- Webhook, Splunk HEC, syslog over UDP, TCP or TLS
- JSON or CEF, with EPSS and KEV fields
- HMAC signed webhooks, SSRF guarded
- Queued with backoff, retries visible per integration
- SMTP or Microsoft Graph email, as digests
In the documentation
- Integrations: webhooks, Splunk and syslog Administrator Guide
- Name, branding and email Administrator Guide
Goes well with
- Audit trail Every sign in and every change, with before and after, who, from where, and whether it worked.
- Kill switch Take a package, a version range, one file hash or a whole advisory away from everyone, at once.
- Malware scanning ClamAV, a hash blocklist, your own scanner and the OpenSSF known malicious feed, on every cached file. Optionally before the first download.
One container, about two minutes
A Linux box with Docker, or one without it, and a reverse proxy for TLS. The installer does the rest and it is safe to run twice. Free, MIT licensed, nothing to sign up for.