@adia-ai/a2ui-mcp
AdiaUI A2UI MCP server. Exposes the compose engine over MCP with an engine selector for monolithic + zettel strategies.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@adia-ai/llm | AI (phantom-deps): Same-org dep; likely used indirectly via sibling packages in the monorepo. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Fires in a smoke-test script only; spreads process.env to add a port var for spawning a local server — not a data exfiltration risk. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): All raw-IP references are 127.0.0.1 (localhost) in test/render scripts — not external network calls. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a declared runtime dep for the MCP HTTP server; phantom-dep heuristic may miss dynamic/conditional imports. | ai | |
| phantom-deps | phantom-dep:@adia-ai/a2ui-corpus | AI (phantom-deps): Same-org sibling dep in a monorepo; likely re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:@adia-ai/a2ui-compose | AI (phantom-deps): Same-org sibling dep in a monorepo; likely re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:@adia-ai/a2ui-retrieval | AI (phantom-deps): Same-org sibling dep in a monorepo; likely re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:@adia-ai/a2ui-validator | AI (phantom-deps): Same-org sibling dep in a monorepo; likely re-exported or used indirectly. | ai |
Versions (showing 26 of 127)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 7 / 0 | |
| 0.4.2 | 7 / 0 | |
| 0.4.1 | 7 / 0 | |
| 0.4.0 | 7 / 0 | |
| 0.3.6 | 7 / 0 | |
| 0.3.5 | 7 / 0 | |
| 0.3.4 | 7 / 0 | |
| 0.3.3 | 7 / 0 | |
| 0.3.2 | 7 / 0 | |
| 0.3.1 | 7 / 0 | |
| 0.3.0 | 7 / 0 | |
| 0.2.5 | 6 / 0 | |
| 0.2.4 | 6 / 0 | |
| 0.2.3 | 6 / 0 | |
| 0.2.2 | 6 / 0 | |
| 0.2.1 | 6 / 0 | |
| 0.2.0 | 6 / 0 | |
| 0.1.3 | 6 / 0 | |
| 0.1.2 | 6 / 0 | |
| 0.1.1 | 6 / 0 | |
| 0.1.0 | 6 / 0 | |
| 0.0.5 | 6 / 0 | |
| 0.0.4 | 6 / 0 | |
| 0.0.3 | 6 / 0 | |
| 0.0.2 | 6 / 0 | |
| 0.0.1 | 6 / 0 |
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
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.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.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.