js-audit

Auditing JavaScript stdlib modules for sandbox safety involves scanning code to identify security vulnerabilities, input validation flaws, and sandbox boundary regressions. This Skill generates a comprehensive report covering correctness and cross-language API consistency for Hull modules.

Static analysis for JavaScript security is the process of reviewing source code without execution to detect vulnerabilities and correctness issues. Use it before shipping stdlib modules to production to enforce sandbox boundaries, error handling, and API parity.

Checking cross-language API parity involves comparing JavaScript stdlib modules against Lua implementations to detect inconsistencies. This Skill enforces parity checks during the audit, ensuring JavaScript and Lua APIs maintain matching functional behavior and security standards.

Yes, static analysis can detect input validation and error handling regressions in Hull JS code. The audit scans stdlib modules and test fixtures to identify missing validation, improper error handling, and sandbox boundary violations that could compromise secure agent execution.

Hardening Hull JavaScript stdlib code requires a comprehensive security and correctness audit. The best approach is running static analysis that checks sandbox boundaries, input validation, error handling, and Lua API parity to generate an actionable security report before production release.

JavaScript stdlib audits show sandbox boundary violations when test fixtures or modules contain improper input validation or error handling. The audit detects these regressions by scanning related test patterns alongside the Hull JS stdlib code to prevent security issues during agent execution.