Versioned security assessment

Report ID: SA-2DEACC81

6/28/2026, 4:06:02 PM

bodhi-sdk-react-integration security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
bodhi-sdk-react-integration
Version
v6
Maintainer
BodhiSearch
Source
github.com/BodhiSearch/bodhi-js/tree/main/bodhi-js-sdk/skills/react-integration
Coverage
6 Files scanned · 2,475 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

1 confirmed security finding requires attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static analysis heavily overcounted Markdown code fences as Ruby backtick execution and marked documentation URLs as risky network behavior. Human review found no prompt injection or confirmed malicious intent, but the skill can run npm/npx commands and includes troubleshooting guidance that may expose OAuth token state in browser storage or console logs.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

6 Files scanned · 2,475 Lines analyzed

4 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 5 evidence locations

Filesystem access

May read or write local files.

Observed in 3 evidence locations

Env variables

May read values from the process environment.

Observed in 5 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 6 evidence locations

Capability review items (3)
Medium
SKILL.md:7SKILL.md:23quick-start.md:14-15quick-start.md:174-175troubleshooting.md:393
Permitted npm and npx Command Execution
The skill allows Bash execution for npm and npx and instructs users to install packages, run dev servers, build apps, and preview deployments. These commands are expected for a React integration skill, but they execute project scripts and dependency lifecycle hooks.
The allowed-tools declaration and setup guides clearly authorize npm and npx usage. The commands are normal for this task, but npm scripts can execute arbitrary code from the target project or dependencies.
Low
SKILL.md:45-48quick-start.md:20-27oauth-setup.md:7-12github-pages.md:128-134troubleshooting.md:503-505
Hardcoded URLs Point to Expected Services
The hardcoded URLs identify Bodhi developer, OAuth, GitHub Pages, Vite, and localhost endpoints needed for setup and troubleshooting. They are not evidence of covert network exfiltration, but users should verify service domains before entering credentials.
The URLs are presented as configuration endpoints for the documented SDK integration. I found no encoded payloads, hidden destinations, or instructions to send secrets to unrelated services.
Low
code-examples.md:627-642github-pages.md:115-126oauth-setup.md:99-147troubleshooting.md:411-418
Environment Variable Examples Are Public Client Configuration
The skill documents Vite environment variables and GitHub Actions secrets for OAuth client IDs and redirect URIs. These examples do not contain real secrets, but users should avoid committing production-specific values when their policy treats client IDs as sensitive.
The examples use placeholder client IDs and standard Vite public variables. OAuth client IDs are often public identifiers, but deployment teams may still classify them as sensitive configuration.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (1)

RISK-001 Medium
troubleshooting.md:137-148troubleshooting.md:199-202troubleshooting.md:437-443troubleshooting.md:454-462oauth-setup.md:165-170
OAuth Token State May Be Exposed During Troubleshooting
The troubleshooting guide recommends logging authentication state and reading localStorage values that may contain access tokens. This is legitimate debugging guidance, but users could accidentally share sensitive token data in logs or issue reports.
The cited lines explicitly show auth state containing an accessToken and localStorage reads for Bodhi auth keys. I did not find evidence that the skill exfiltrates those values, so the risk is exposure through debugging rather than malicious collection.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (1)
Low
code-examples.md:9-24github-pages.md:77-88oauth-setup.md:29-47quick-start.md:14-15SKILL.md:54-56
Static Command Findings Are Markdown False Positives
The analyzer reported many Ruby backtick executions, but reviewed locations are Markdown fenced code blocks containing TypeScript, TSX, shell snippets, or prose. No Ruby backtick execution pattern was confirmed in executable skill code.
Line-number review showed Markdown code fences and inline documentation, not Ruby code execution. The files are documentation-only, although some examples instruct users to run legitimate shell commands.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable