@etohq/ambassador
Eto Ambassador Program module
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:awilix | AI (phantom-deps): Declared as runtime dep; referenced via config/DI container pattern in a monorepo module, not a direct import. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/core | AI (phantom-deps): ORM peer dep referenced in config files; standard monorepo/DI pattern. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/migrations | AI (phantom-deps): ORM migrations dep referenced in config files; standard monorepo/DI pattern. | ai |
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.