Evidence for AI clean decision
- The manifest describes a global Xema CLI, with `dist/cli.js` as its entry point and bin.
- The CLI starts its command handler only when executed as the main module; importing it does not call `main()`.
- Control-plane credentials are resolved alongside an endpoint supplied through flags, environment, or a saved Xema session.
- The inspected API calls send the token to that target endpoint for explicit biome installation or capability invocation.
- Support bundles redact configuration and desired-plan values and mark included content as false.
Evidence against
- The package includes filesystem, process, and network operations, but the inspected uses support CLI commands and worker lifecycle management.
- The scanner flagged a possible secret pattern and source similarity; the inspected support-bundle code redacts values, and the flagged bundle is accompanied by provenance metadata.
Behavioral surface
SourceChild process · Crypto · Dynamic require · Environment variables · Eval · Filesystem · Network
Supply chainHigh entropy strings · URL strings
ManifestNo manifest risk signals triggered.
Scanned 301 files · 5.15 MB of source
14 external domains referenced
- 127.0.0.1
- accounts.google.com
- github.com
- in-toto.io
- json-schema.org
- login.microsoftonline.com
- oauth2.googleapis.com
- oras.land
- registry.npmjs.org
- sigstore.dev
- slsa.dev
- spdx.dev
- token.actions.githubusercontent.com
- xema.dev