@layerzerolabs/onesig-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:typechain-types/factories/@openzeppelin/contracts/utils/cryptography/ECDSA__factory.ts | AI (source-diff): EVM bytecode hex in typechain factory files is standard Hardhat compilation output, not obfuscation. | ai | |
| source-diff | encoded-string-file:typechain-types/factories/@openzeppelin/contracts/utils/cryptography/MerkleProof__factory.ts | AI (source-diff): EVM bytecode hex in typechain factory files is standard Hardhat compilation output, not obfuscation. | ai | |
| source-diff | encoded-string-file:typechain-types/factories/contracts/mocks/MockOApp__factory.ts | AI (source-diff): EVM bytecode hex in typechain factory files is standard Hardhat compilation output, not obfuscation. | ai | |
| source-diff | encoded-string-file:typechain-types/factories/contracts/OneSig__factory.ts | AI (source-diff): EVM bytecode hex in typechain factory files is standard Hardhat compilation output, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package from LayerZero Labs; missing metadata is expected for org-internal packages. | ai |
Versions (showing 6 of 106)
| Version | Deps | Published |
|---|---|---|
| 0.0.6 | 2 / 41 | |
| 0.0.5 | 2 / 41 | |
| 0.0.4 | 2 / 41 | |
| 0.0.3 | 1 / 46 | |
| 0.0.2 | 0 / 48 | |
| 0.0.1 | 0 / 47 |
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.