@mentra/soga
SOGA - Smart Orchestration Glasses Agent. Desktop daemon for AI-powered coding via AR smart glasses.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @mentra package for an AR agent product; Levenshtein match to 'koa' is coincidental, not impersonation. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env-spread used to pass process.env to a child process — standard pattern, not credential exfiltration. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Simple decode utility with no network sink; base64 is used for secrets storage/retrieval, not payload obfuscation. | ai | |
| phantom-deps | phantom-dep:@google/generative-ai | AI (phantom-deps): @google/generative-ai is listed in dependencies in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 2 / 3 | |
| 0.1.3 | 2 / 3 | |
| 0.1.2 | 2 / 3 | |
| 0.1.1 | 2 / 3 | |
| 0.1.0 | 2 / 3 |
v0.1.4
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/mentra-app/soga/blob/1f2791b1023fe38d51c4728db4dd2e07685c1d45/src/terminal-agent.ts#L216 214 | stdout: "pipe", 215 | stderr: "pipe", > 216 | env: { 217 | ...process.env, 218 | ...providerEnv,
Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.