executable-stories-cypress@8.9.5
BDD-style executable stories for Cypress with documentation generation
AI Security Review
scanned 17h ago · by lpm-firewall-aiThe package has no install hook, and the inspected runtime reporter performs test-result collection and report generation. The scanner’s runtime hints resolve to local in-memory store helpers and optional raw report file output, with no confirmed attack behavior.
Decision evidence
public snapshot- package.json has no install lifecycle hook; its scripts are build, type-check, and tests.
- The reporter collects Cypress results and invokes report generation when the runner ends; writing a raw run is conditional on a configured path.
- The reporter imports the formatter library, while the inspected core helper only validates and returns a documentation entry.
- The formatter CLI is a separate executable entrypoint; no evidence shows this Cypress package invoking it automatically.
Source & flagged code
8 flagged · loading sourcepackage.json has no install lifecycle hook; its scripts are build, type-check, and tests.
package.jsonView on unpkg · L63The reporter collects Cypress results and invokes report generation when the runner ends; writing a raw run is conditional on a configured path.
dist/reporter.cjsView on unpkg · L107Findings
Affected versions and remediation
This report applies to executable-stories-cypress@8.9.5.
See all versions of executable-stories-cypress for other recorded verdicts.
- Review the evidence and your use of executable-stories-cypress@8.9.5 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.