Summary
ahmedk95/forgemax v2026-03-22 was classified as CRITICAL RISK with a risk score of 652. Sigil detected 41 findings across 86 files, covering phases including provenance, code patterns, install hooks, obfuscation, credential access. Review the findings below before installing this package.
Package description: Collapse multiple servers and tools into two sandboxed MCP tools for efficient, typed JavaScript execution with secure resource access and concurrency.
v2026-03-22
22 March 2026, 23:45 UTC
by Sigil Bot
Risk Score
652
Findings
41
Files Scanned
86
Provenance
Repository
https://github.com/ahmedk95/forgemaxScanned From
https://github.com/ahmedk95/forgemax.gitFindings by Phase
Phase Ordering
Phases are ordered by criticality, with the most dangerous at the top. Click any phase header to expand or collapse its findings. Critical phases are expanded by default.
install-makefile-curl
HIGHMakefile/script pipes remote content to shell
repo/CONTRIBUTING.md:95
8. Verify CI: checksums, SBOM, all platforms green
9. Verify install: `curl -fsSL .../install.sh | bash` on a fresh machine
10. Publish npm: `cd npm && npm publish`Why was this flagged?
A script or Makefile pipes content from a remote URL directly into a shell (curl | sh or wget | bash). This is inherently dangerous because the remote content can change at any time, and the command runs with the current user's permissions. Rated HIGH because it requires manual execution (unlike install hooks) but still executes arbitrary remote code.
install-makefile-curl
HIGHMakefile/script pipes remote content to shell
repo/install.sh:5
# Forgemax installer — downloads pre-built binaries from GitHub releases.
# Usage: curl -fsSL https://raw.githubusercontent.com/postrv/forgemax/main/install.sh | bash
Why was this flagged?
A script or Makefile pipes content from a remote URL directly into a shell (curl | sh or wget | bash). This is inherently dangerous because the remote content can change at any time, and the command runs with the current user's permissions. Rated HIGH because it requires manual execution (unlike install hooks) but still executes arbitrary remote code.
install-npm-postinstall
CRITICALnpm lifecycle script — runs automatically on install
repo/npm/package.json:23
"scripts": {
"postinstall": "node install.js"
},Why was this flagged?
npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.
Badge
Markdown
[](https://sigilsec.ai/scans/10BB25CC-DCBB-4FDC-843A-0111BCDCF4F0)HTML
<a href="https://sigilsec.ai/scans/10BB25CC-DCBB-4FDC-843A-0111BCDCF4F0"><img src="https://sigilsec.ai/badge/github/ahmedk95/forgemax" alt="Sigil Scan"></a>Run This Scan Yourself
Scan your own packages
Run Sigil locally to audit any package before it touches your codebase.
Early Access
Get cloud scanning, threat intel, and CI/CD integration.
Join 150+ developers on the waitlist.
Get threat intelligence and product updates
Security research, new threat signatures, and product updates. No spam.
Other github scans
Believe this result is incorrect? Request a review or see our Terms of Service and Methodology.