resuggestor
Cursor skill for frontend performance optimization — install with npm and use /resuggestor in chat
This report shows the evidence for resuggestor@1.0.1. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms automatic postinstall writes to .cursor hooks.json and an executable hook that injects agent instructions, which meets the firewall policy for blocking unconsented install-time mutation of a broad AI-agent control surface. Other risky primitives appear user-invoked or package-aligned, but they do not neutralize the postinstall control-surface mutation. Product guard normalized a concrete AI-agent control hijack publish_block to the blockable dangerous-capability shape.
Decision evidence
public snapshot- package.json runs postinstall: node install.js.
- install.js calls installSkillFiles during npm install.
- lib/copy.mjs copies templates/.cursor/hooks into project .cursor/hooks and merges .cursor/hooks.json.
- templates/.cursor/hooks.json registers postToolUse Write hook.
- resuggestor-post-canvas-write.sh injects additional_context into Cursor after matching Write operations.
- No credential harvesting or exfiltration found in install path.
- GitLab token handling is prompted/user-configured and used for GitLab API calls.
- chrome-devtools-mcp global install is interactive configure-time, not automatic postinstall.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to resuggestor@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing resuggestor@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.