Versioned security assessment
Report ID: SA-483A89F4
7/5/2026, 6:20:36 AM
react-native-best-practices security assessment v3
Skill Security Certification Report
- Skill name
- react-native-best-practices
- Version
- v3
- Maintainer
- callstackincubator
- Coverage
- 29 Files scanned · 6,499 Lines analyzed
- Policy version
- Unavailable
Highest confirmed finding severity
Critical
3 confirmed security findings require 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 pageThis report does not block or authorize the manifest or ZIP.
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
29 Files scanned · 6,499 Lines analyzed
8 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.
Source
Binding unavailable
Artifact
Identity incomplete
Audit
Complete
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.
Observed in 7 evidence locations
Network access
May connect to external services.
Observed in 6 evidence locations
Filesystem access
May read or write local files.
Observed in 11 evidence locations
Env variables
May read values from the process environment.
Observed in 1 evidence location
External commands
May invoke commands or programs outside the Skill.
Observed in 63 evidence locations
Capability review items (5)
Risk findings
Confirmed security concerns are separated from items that still need review.
Confirmed security concerns (3)
Remediation
Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.
- FIX-001CriticalRemote installer is piped directly into bash.Replace curl-to-bash instructions with a package manager install, a signed release download, or checksum verification before execution.
- FIX-002HighRemote code loading examples lack trust controls.Add guidance for signed chunks, integrity validation, allowlisted hosts, rollback controls, and App Store or Play policy review.
- FIX-003MediumLocal shell commands are presented without execution safeguards.State that commands should run only with user approval in the project root, and explain what files or build outputs they change.
- FIX-004LowBinary screenshots require manual review during marketplace audits.Keep images as simple documentation assets, strip unnecessary metadata, and avoid embedding instructions or secrets in screenshots.
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 (2)
Verify and export
The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.
Audit attestation: not_attestable