@autonoma-io/code
Autonoma Code v4.0 - AI-powered development platform with 28 specialized agents, LSP integration, and background task execution
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:cors | AI (typosquat): Scoped package @autonoma-io/code; Levenshtein match to 'cors' is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @autonoma-io/code; Levenshtein match to 'zod' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-ecs | AI (phantom-deps): AWS SDK clients loaded by convention in a CLI tool; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-rds | AI (phantom-deps): AWS SDK clients loaded by convention in a CLI tool; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-lambda | AI (phantom-deps): AWS SDK clients loaded by convention in a CLI tool; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-cloudwatch-logs | AI (phantom-deps): AWS SDK clients loaded by convention in a CLI tool; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): yargs referenced in config files; consistent with CLI tool pattern. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): winston referenced in config files; consistent with logging setup pattern. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 18 / 27 | |
| 3.0.2 | 18 / 27 | |
| 3.0.1 | 18 / 27 | |
| 3.0.0 | 18 / 27 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.