Index of every page on this site: llms.txt
All skills
openai avatar

/publish-findings

@ec0d6c1
by openaiopenai/codex-security14k stars
1,108
Run it yourself

Import findings from scanners, CI reports, vendor CLIs, APIs, or connected tools into the local workbench. Publish a selection of stored vendor findings to Codex Security Cloud.

Use this Skill: https://skilld.dev/gh/openai/codex-security/publish-findings

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referenceswiz-import.md

≈1.3k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Wiz import reference

Finding formats

The importer reads JSON, normalized JSONL, and the repository package-vulnerability CSV profile below, with gzip supported for each format. Direct CSV support covers repository package vulnerabilities (SCA) only. It does not fetch from Wiz or accept other CSV profiles, scan events, workload secrets, cloud configuration, or external network exports. Complete the requested pages; for an explicit subset, preserve the selection and its named collection.

Keep raw source records unchanged in source_data. Use the vendor occurrence ID, not a rule, CVE, title, or location. Missing IDs, severity, revisions, and locations must not be invented.

For Cloud preview, approval, upload, and recovery, follow the Cloud publication workflow.

Package vulnerabilities

Supported inputs include a vulnerability finding, an array, data.vulnerabilityFindings.nodes, a downloaded vulnerability report, and JSONL package records. Keep id, name, detailedName, vendorSeverity (or severity), and vulnerableAsset.id, with available package and source metadata. Use the bare Wiz finding ID for a package occurrence.

For a UI export, use Vulnerability Findings → Save as → Report, retaining repository and finding filters. Select Repository Branch, JSON or comma-separated CSV, and Detailed columns. Pass supported CSV reports directly to the command. Download the completed report; gzip is supported regardless of the filename extension. Raw Event on Code & Build Scans contains scan metadata, not findings. Do not create scheduled reports, notifications, or external storage unless requested.

The CSV profile requires ID, Name, DetailedName, AssetID, WizURL, CloudPlatform, and CloudProviderURL. CloudPlatform must identify GitHub, and CloudProviderURL must be a repository-branch URL. Its repository must match the selected Cloud repository or, for local import, a Git remote when parseable remotes are available. The importer uses the reported ID as occurrence identity and retains every original cell, including unknown columns, in source_data.row. It does not derive a branch or revision from the tree URL. Review excluded rows in the preview before importing.

SAST, repository secrets, and IaC

Retain the named collection; bare arrays cannot identify these finding families.

Family Collection Occurrence ID
SAST data.sastFindings.nodes sast:<id>
Repository secrets data.secretInstances.nodes secret:<id>
IaC data.iacFindings.nodes iac:<id>

Supply a verified repository.url in the source repository metadata or matching repository.id and repository.url in data.versionControlResources.nodes. For secrets, the repository is resource.typedProperties.repository and the resource type must be REPOSITORY_BRANCH. Keep inventory platform: explicit GITHUB enables case-insensitive matching on custom GitHub Enterprise hosts.

Resolve conflicting platform or URL metadata for a repository ID before publishing. Names, inventory node IDs, providerID, and Wiz UUIDs are not Cloud repository IDs. The importer checks source URLs against the selected destination; fix missing or conflicting mappings before upload.

Normalized JSONL and CSV conversion

Normalized JSONL has one record per line with source_finding_id and evidence containing title, severity, and the original record in source_data. For SAST, secrets, and IaC, also set evidence.details.kind to sast, secret, or iac and set the verified evidence.details.repository.url. Use the same prefixed occurrence IDs as raw API imports.

SAST, repository-secret, and IaC CSV reports require a reviewed mapping of their actual headers into that profile. Preserve these family-specific details when present:

Family Evidence to retain
SAST Rule/CWE, source range and snippet, scanner origin and verdict, remediation instructions
Repository secrets Source path and line, detector rule, type and confidence, vendor validation status, encryption/management flags, introduced commit
IaC Rule IDs/name, source range and matched content, platform, expected/actual content, file link, remediation instructions

Select source paths and line numbers explicitly for secret reports; the standard metadata query lacks them. Preserve empty IaC comparison strings. Vendor status, AI verdicts, and secret validation remain vendor evidence, not Codex assessments. An introduced commit is not a scanned revision, and a logical IaC resource does not prove runtime deployment.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warningtoday3 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill facilitates the import and publication of security findings from various third-party scanners. It uses local command-line tools and custom scripts to process scanner reports. The skill includes robust security practices, such as environment isolation, path validation, and binary integrity checks.

  • Sockettoday

    No alerts

  • Snyktoday

    Risk: MEDIUM · 1 issue

Signed by skilld at ec0d6c1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago

README badge

README badge for openai/codex-security/publish-findings