@agimon-ai/model-proxy-mcp
Claude-compatible model proxy MCP with ChatGPT Codex upstream support
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/stdio-B-atmzW4.cjs | AI (source-diff): Standard bundler CJS output; readable logic visible in sample. | ai | |
| source-diff | obfuscated-file:dist/stdio-BxbGlLys.mjs | AI (source-diff): Standard bundler ESM output; readable logic visible in sample. | ai | |
| source-diff | obfuscated-file:dist/stdio-xpvsxU_k.mjs | AI (source-diff): Standard tsdown/rollup bundle output; code is readable minification, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/stdio-BKQRhaEs.cjs | AI (source-diff): Standard tsdown/rollup bundle output; code is readable minification, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/stdio-c0HJnrrl.mjs | AI (source-diff): ESM bundle counterpart; same pattern as CJS bundle, no malicious content. | ai | |
| source-diff | obfuscated-file:dist/stdio-DHpnYu_d.cjs | AI (source-diff): Standard bundler output; samples show expected dependencies and proxy logic. | ai | |
| source-diff | obfuscated-file:dist/stdio-CKoJlBdM.mjs | AI (source-diff): Standard tsdown/Vite minified bundle output; code content is benign MCP proxy logic. | ai | |
| source-diff | obfuscated-file:dist/stdio-D5p7q_0H.cjs | AI (source-diff): Standard tsdown/Vite minified bundle output; code content is benign MCP proxy logic. | ai | |
| source-diff | obfuscated-file:dist/cli.cjs | AI (source-diff): Standard tsdown/Rollup minified bundle; code is readable and benign in samples. | ai | |
| source-diff | obfuscated-file:dist/stdio-CffHO4FT.cjs | AI (source-diff): Standard tsdown/Rollup minified bundle; code is readable and benign in samples. | ai | |
| source-diff | obfuscated-file:dist/stdio-P-s6QuNu.mjs | AI (source-diff): Standard tsdown/Rollup minified bundle; code is readable and benign in samples. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config-driven validation; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Config parsing; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): Web framework for MCP server; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): Core MCP SDK; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:@hono/node-server | AI (phantom-deps): Hono adapter; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): Runtime metadata; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:better-sqlite3 | AI (phantom-deps): Database; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI framework; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:ulidx | AI (phantom-deps): ID generation; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:@agimon-ai/foundation-port-registry | AI (phantom-deps): Same-org internal dep; bundled tool pattern. | ai | |
| phantom-deps | phantom-dep:@agimon-ai/foundation-process-registry | AI (phantom-deps): Same-org internal dep; bundled tool pattern. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 11 / 5 | |
| 0.10.5 | 11 / 5 | |
| 0.10.4 | 11 / 5 | |
| 0.10.3 | 11 / 5 | |
| 0.10.2 | 11 / 5 | |
| 0.10.1 | 11 / 5 | |
| 0.10.0 | 11 / 5 | |
| 0.9.7 | 11 / 5 | |
| 0.9.6 | 11 / 5 | |
| 0.9.5 | 11 / 5 | |
| 0.9.4 | 11 / 5 | |
| 0.9.3 | 11 / 5 | |
| 0.9.1 | 11 / 5 | |
| 0.9.0 | 11 / 5 | |
| 0.8.7 | 11 / 5 | |
| 0.8.6 | 11 / 5 | |
| 0.8.5 | 11 / 5 | |
| 0.8.4 | 11 / 5 | |
| 0.8.3 | 11 / 5 | |
| 0.8.2 | 11 / 5 | |
| 0.8.0 | 11 / 5 | |
| 0.7.0 | 11 / 5 | |
| 0.6.0 | 11 / 5 | |
| 0.5.3 | 11 / 5 | |
| 0.5.2 | 11 / 5 | |
| 0.5.1 | 11 / 5 | |
| 0.5.0 | 11 / 5 | |
| 0.4.0 | 11 / 5 | |
| 0.3.1 | 11 / 5 | |
| 0.3.0 | 11 / 5 | |
| 0.2.17 | 10 / 5 | |
| 0.2.16 | 10 / 5 | |
| 0.2.15 | 10 / 5 | |
| 0.2.14 | 10 / 5 | |
| 0.2.12 | 10 / 5 | |
| 0.2.11 | 10 / 5 | |
| 0.2.10 | 10 / 5 | |
| 0.2.9 | 10 / 5 | |
| 0.2.8 | 10 / 5 | |
| 0.2.7 | 10 / 5 | |
| 0.2.6 | 10 / 5 | |
| 0.2.5 | 10 / 5 | |
| 0.2.4 | 10 / 5 | |
| 0.2.3 | 10 / 5 | |
| 0.2.2 | 10 / 5 | |
| 0.2.1 | 10 / 5 | |
| 0.2.0 | 10 / 5 |
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.