@layerzerolabs/onesig-evm

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

layerzero-bot

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	2026/05/31
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	2026/05/31
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	2026/05/31
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	2026/05/31
bogus-package	bogus-package	AI (bogus-package): Internal monorepo package from LayerZero Labs; missing metadata is expected for org-internal packages.	ai	2026/05/14

Versions (showing 51 of 52)

View all versions

Version	Deps	Published
0.2.102	2 / 30	2026-06-05
0.2.101	2 / 30	2026-05-27
0.2.100	2 / 30	2026-05-25
0.2.99	2 / 30	2026-05-22
0.2.98	2 / 30	2026-05-21
0.2.97	2 / 30	2026-05-20
0.2.96	2 / 30	2026-05-20
0.2.95	2 / 30	2026-05-20
0.2.94	2 / 30	2026-05-19
0.2.93	2 / 30	2026-05-15
0.2.92	2 / 30	2026-05-14
0.2.90	2 / 31	2026-05-07
0.2.88	2 / 31	2026-05-06
0.2.87	2 / 31	2026-05-05
0.2.86	2 / 31	2026-05-05
0.2.85	2 / 31	2026-05-04
0.2.84	2 / 31	2026-05-01
0.2.83	2 / 31	2026-04-30
0.2.82	2 / 31	2026-04-28
0.2.81	2 / 31	2026-04-24
0.2.80	2 / 31	2026-04-22
0.2.79	2 / 31	2026-04-20
0.2.78	2 / 31	2026-04-16
0.2.77	2 / 31	2026-04-15
0.2.76	2 / 31	2026-04-15
0.2.75	2 / 31	2026-04-14
0.2.74	2 / 31	2026-04-14
0.2.73	2 / 31	2026-04-14
0.2.72	2 / 31	2026-04-14
0.2.71	2 / 31	2026-04-13
0.2.70	2 / 31	2026-04-13
0.2.69	2 / 31	2026-04-13
0.2.68	2 / 31	2026-04-10
0.2.67	2 / 31	2026-04-09
0.2.66	2 / 31	2026-04-09
0.2.65	2 / 31	2026-04-06
0.2.64	2 / 31	2026-04-01
0.2.63	2 / 31	2026-03-31
0.2.62	2 / 31	2026-03-30
0.2.61	2 / 31	2026-03-28
0.2.60	2 / 31	2026-03-27
0.2.59	2 / 31	2026-03-25
0.2.56	2 / 31	2026-03-20
0.2.50	2 / 31	2026-03-12
0.2.48	2 / 31	2026-03-11
0.2.47	2 / 31	2026-03-10
0.1.1	2 / 35	2025-08-01
0.1.0	2 / 34	2025-07-16
0.0.14	2 / 34	2025-05-27
0.0.13	2 / 36	2025-05-01
0.0.12	2 / 41	2025-04-29

v0.2.102

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.101

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.100

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.99

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.98

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.97

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.96

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.95

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.94

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.93

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.92

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.90

6 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: layerzero-bot.

HIGH Long encoded string in modified file: typechain-types/factories/@openzeppelin/contracts/utils/cryptography/ECDSA__factory.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: typechain-types/factories/@openzeppelin/contracts/utils/cryptography/MerkleProof__factory.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: typechain-types/factories/contracts/mocks/MockOApp__factory.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: typechain-types/factories/contracts/OneSig__factory.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.88

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.87

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.86

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.85

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.84

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.83

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.81

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.80

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.79

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.78

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.77

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.76

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.75

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.74

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.73

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.72

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.71

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.70

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.69

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.68

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.67

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.66

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.65

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.64

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.63

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.62

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.61

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.60

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.59

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.56

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.48

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.47

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

2 findings

HIGH Long encoded string in modified file: typechain-types/factories/contracts/OneSig__factory.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

5 findings