@mobile-reality/mdma-cli
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/prompts/anthropic/_shared.d.ts | AI (source-diff): Long lines are AI prompt template strings in TypeScript declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/prompts/anthropic/haiku.d.ts | AI (source-diff): Long lines are AI prompt template strings in TypeScript declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/prompts/anthropic/opus.d.ts | AI (source-diff): Long lines are AI prompt template strings in TypeScript declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/prompts/anthropic/sonnet.d.ts | AI (source-diff): Long lines are AI prompt template strings in TypeScript declarations, not obfuscated code. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): yaml is a declared runtime dep used in config handling; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@mobile-reality/mdma-spec | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.6 | 9 / 16 | |
| 0.2.5 | 9 / 16 | |
| 0.2.4 | 9 / 16 | |
| 0.2.3 | 9 / 16 | |
| 0.2.2 | 9 / 16 | |
| 0.2.1 | 9 / 16 | |
| 0.2.0 | 9 / 16 | |
| 0.1.4 | 9 / 16 | |
| 0.1.3 | 9 / 13 | |
| 0.1.2 | 9 / 13 | |
| 0.1.1 | 9 / 13 | |
| 0.1.0 | 9 / 13 |
v0.2.6
5 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.
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
5 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.
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
5 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.
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. 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.4
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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.