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.

referencescheckmarx-import.md

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

Collect and import Checkmarx SAST findings

Use a supplied One CLI JSON or CxSAST XML report directly. For collection, confirm the product, tenant or server, completed scan ID, project, repository URL and ref. Both collectors retrieve the full scan. If the operator wants a subset, ask for an export scoped to that selection.

Before launching a vendor tool

  • Use a trusted session and a private working and temporary directory outside the source tree, for both local and Cloud imports. Set the working directory before starting a process. Use a noninteractive, non-login system shell such as /bin/sh with login: false.
  • If an IDE or build supplies checkout-controlled startup settings, use a known-clean session or a saved export. A trusted host can exclude LD_*, DYLD_*, BASH_ENV and ENV before launching a shell or interpreter. Keep existing exclusions and account for restored shell snapshots. Never start a suspect shell to unset variables or source project files. Codex shell environment policy
  • Resolve the installed collector and vendor tools to trusted absolute paths outside the source tree. For python_path, use trusted system tools to inspect the executable and resolve symlinks without running it. Use the native Python 3.10+ interpreter with -I -S. Ask for native installation paths if given a shim or shell launcher.
  • Pass the absolute checkout or unpacked source as --source-root before the product. Omit it only when there is no local source tree.

Checkmarx One

Use native cx 2.3.23+. An explicit CX_CONFIG_FILE_PATH selects that trusted profile. Without an explicit profile, the helper uses a complete environment login if present, or ~/.checkmarx/checkmarxcli.yaml. For an environment login, confirm the destination and keep CX_APIKEY or CX_CLIENT_ID, CX_CLIENT_SECRET, CX_BASE_URI and CX_TENANT in the operator's environment. A separate OAuth server also uses CX_BASE_AUTH_URI. For an older client or a credential-store-only login with no profile file, ask for JSON exported with the operator’s usual setup.

cx results show retrieves every engine in a mixed scan and can generate and download an SCA package report. Checkmarx One results

"$python_path" -I -S "$collector" --source-root "$source_root" one "$scan_id" --cx "$cx_path"

Self-managed CxSAST

Verify ownership before fetching. CxFlow requests XML by scan ID. Confirm the completed ID, exact project and full owning team path from the same Projects & Scans → All Scans row on the selected server. Use trusted read-only metadata or ask the operator to confirm those values from that view. For repeated names, check View Project Scans under the intended team. Without confirmation, ask for selected XML. Issue-tracker filters do not narrow the raw XML. All Scans

Use native Java, a released CxFlow JAR (1.6.37+), and a trusted SAST-only profile with CxXml enabled. Keep the profile and everything it loads outside the checkout. Take the server, authentication and any custom checkmarx.client-id from that profile. Only append --use-env-credentials when the operator confirms the session's CHECKMARX_USERNAME, CHECKMARX_PASSWORD or CHECKMARX_CLIENT_SECRET belong to that server. For custom JVM settings or project names the installed CxFlow cannot resolve, ask for an XML export. CxFlow credentials · CxXml writer

"$python_path" -I -S "$collector" --source-root "$source_root" cxsast "$scan_id" \
  --java "$java_path" --jar "$jar_path" --config "$config_path" --team "$cx_team" --project "$cx_project"

Preview and import

Pass the successful helper's printed path as the quoted file argument to codex-security publish findings in the next tool call. Use --provider checkmarx --to local --repository CHECKOUT, the verified --source-repository-url, a stable product/tenant/project/ref --source-key, and --dry-run --format json. Review the scope, findings and exclusions. Verify native paths against the checkout before opening source files.

After confirmation, reuse that file and those options for the local import. Use its stored selection for Cloud publication and retries. Remove the helper’s temporary directory after readback unless the operator wants it retained. Keep operator-supplied files. User guide

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