@agimon-ai/imagine-mcp
MCP server for AI image generation and manipulation
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config-referenced validation library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): CLI output formatting; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:sharp | AI (phantom-deps): Image processing binary; known implicit runtime dependency. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Config-referenced web framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:libheif-js | AI (phantom-deps): Image format support; config-referenced dependency. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): HTTP client; config-referenced dependency. | ai | |
| phantom-deps | phantom-dep:unsplash-js | AI (phantom-deps): API client; config-referenced dependency. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-s3 | AI (phantom-deps): Framework-scoped AWS SDK; convention-loaded dependency. | ai | |
| phantom-deps | phantom-dep:@google-cloud/storage | AI (phantom-deps): Framework-scoped GCP SDK; convention-loaded dependency. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): MCP protocol SDK; config-referenced core dependency. | ai | |
| phantom-deps | phantom-dep:@agimon-ai/foundation-validator | AI (phantom-deps): Same-org internal module; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@agimon-ai/foundation-port-registry | AI (phantom-deps): Same-org internal module; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@agimon-ai/foundation-process-registry | AI (phantom-deps): Same-org internal module; stable pattern for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.11.1 | 14 / 5 | |
| 0.11.0 | 14 / 5 | |
| 0.10.5 | 14 / 5 | |
| 0.10.4 | 14 / 5 | |
| 0.10.3 | 14 / 5 | |
| 0.10.2 | 14 / 5 | |
| 0.10.1 | 14 / 5 | |
| 0.10.0 | 14 / 5 | |
| 0.9.7 | 14 / 5 | |
| 0.9.6 | 14 / 5 | |
| 0.9.5 | 14 / 5 | |
| 0.9.4 | 14 / 5 | |
| 0.9.3 | 14 / 5 | |
| 0.9.1 | 14 / 5 | |
| 0.9.0 | 14 / 5 | |
| 0.8.7 | 14 / 5 | |
| 0.8.6 | 14 / 5 | |
| 0.8.5 | 14 / 5 | |
| 0.8.4 | 14 / 5 | |
| 0.8.3 | 14 / 5 | |
| 0.8.2 | 14 / 5 | |
| 0.8.0 | 14 / 5 | |
| 0.7.0 | 14 / 5 | |
| 0.6.0 | 14 / 5 | |
| 0.5.3 | 14 / 5 | |
| 0.5.2 | 13 / 5 | |
| 0.5.1 | 13 / 5 | |
| 0.5.0 | 13 / 5 | |
| 0.4.0 | 13 / 5 | |
| 0.3.1 | 13 / 5 | |
| 0.3.0 | 13 / 5 | |
| 0.2.12 | 13 / 5 | |
| 0.2.11 | 13 / 5 | |
| 0.2.10 | 13 / 5 | |
| 0.2.9 | 13 / 5 | |
| 0.2.7 | 13 / 5 | |
| 0.2.6 | 13 / 5 | |
| 0.2.5 | 13 / 5 | |
| 0.2.4 | 11 / 5 | |
| 0.2.3 | 11 / 5 | |
| 0.2.2 | 11 / 5 | |
| 0.2.1 | 11 / 5 | |
| 0.2.0 | 11 / 5 |
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.