job-forge
AI-powered job search pipeline for Codex and OpenCode
This report shows the evidence for job-forge@2.14.56. 4 of 8 known versions are blocked or flagged. The newest version, 2.14.70, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms concrete postinstall mutation of consumer AI-agent configuration across several platforms. Under the stated policy, this requires blocking even though no direct exfiltration was confirmed.
Decision evidence
public snapshot- package.json runs bin/sync.mjs automatically via postinstall.
- bin/sync.mjs symlinks package-controlled MCP, Codex, Claude, Cursor, OpenCode, and shared-agent files into the consumer project.
- bin/sync.mjs modifies an existing consumer opencode.json and invokes migrations without user action.
- templates/migrations.json automatically merges consumer package.json scripts and .gitignore entries.
- Injected MCP configs configure npx -y @razroo/gmail-mcp@1.8.1 for later agent startup.
- sync.mjs preserves existing real files and conflicting symlinks.
- No source-confirmed credential exfiltration or hidden network endpoint was found in inspected lifecycle code.
- The observed network check in scripts/verify-greenhouse-urls.mjs is an explicit utility, not install-time behavior.
Source & flagged code
15 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a possible secret pattern.
config/profile.example.ymlView on unpkg · L53Hardcoded password in config/profile.example.yml
config/profile.example.ymlView on unpkg · L124Findings
Affected versions and remediation
This report applies to job-forge@2.14.56.
The versions list below shows the verdict for each recorded version.
- Avoid installing job-forge@2.14.56. 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.