@easylayer/evm
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:rlp | AI (phantom-deps): rlp is a declared runtime dep used transitively in EVM context; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a standard NestJS peer dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash declared as runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:piscina | AI (phantom-deps): piscina declared as runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@nestjs/core | AI (phantom-deps): NestJS core is a standard peer dep in NestJS ecosystem packages; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@nestjs/swagger | AI (phantom-deps): NestJS swagger declared as runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a known implicit dep for NestJS/TypeScript decorators; phantom-dep heuristic false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 18 / 10 | |
| 1.0.4 | 18 / 10 | |
| 1.0.3 | 18 / 10 | |
| 1.0.2 | 18 / 10 | |
| 1.0.0 | 18 / 10 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.