@layerzerolabs/onesig-core
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Consistent bot publisher with strong track record; missing gitHead is a CI environment change, not a malware signal for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @layerzerolabs/typescript-utils at matching monorepo version 0.2.74 — consistent same-org coordinated release. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package from LayerZero; missing metadata is a stable pattern across their published packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with LayerZero monorepo publishing pattern; not indicative of malice. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all LayerZero bot-published packages; stable false positive for this publisher. | ai |
Versions (showing 51 of 137)
| Version | Deps | Published |
|---|---|---|
| 1.2.19 | 5 / 8 | |
| 1.2.18 | 5 / 8 | |
| 1.2.17 | 5 / 8 | |
| 1.2.16 | 5 / 8 | |
| 1.2.15 | 5 / 8 | |
| 1.2.14 | 5 / 8 | |
| 1.2.13 | 5 / 9 | |
| 1.2.12 | 5 / 9 | |
| 1.2.11 | 5 / 9 | |
| 1.2.10 | 5 / 9 | |
| 1.2.9 | 5 / 9 | |
| 1.2.8 | 5 / 9 | |
| 1.2.7 | 5 / 9 | |
| 1.2.6 | 5 / 9 | |
| 0.2.133 | 5 / 9 | |
| 0.2.132 | 5 / 9 | |
| 0.2.131 | 5 / 9 | |
| 0.2.130 | 5 / 9 | |
| 0.2.129 | 5 / 9 | |
| 0.2.128 | 5 / 9 | |
| 0.2.127 | 5 / 9 | |
| 0.2.126 | 5 / 9 | |
| 0.2.125 | 5 / 9 | |
| 0.2.124 | 5 / 9 | |
| 0.2.123 | 5 / 9 | |
| 0.2.122 | 5 / 9 | |
| 0.2.121 | 5 / 9 | |
| 0.2.120 | 5 / 9 | |
| 0.2.119 | 5 / 9 | |
| 0.2.118 | 5 / 9 | |
| 0.2.117 | 5 / 9 | |
| 0.2.116 | 5 / 9 | |
| 0.2.115 | 5 / 9 | |
| 0.2.114 | 5 / 9 | |
| 0.2.113 | 4 / 9 | |
| 0.2.112 | 4 / 9 | |
| 0.2.111 | 4 / 9 | |
| 0.2.110 | 4 / 9 | |
| 0.2.109 | 4 / 9 | |
| 0.2.108 | 4 / 9 | |
| 0.2.107 | 4 / 9 | |
| 0.2.106 | 4 / 9 | |
| 0.2.105 | 4 / 9 | |
| 0.2.104 | 4 / 9 | |
| 0.2.103 | 4 / 9 | |
| 0.2.102 | 4 / 9 | |
| 0.2.101 | 4 / 9 | |
| 0.2.100 | 4 / 9 | |
| 0.2.99 | 4 / 9 | |
| 0.2.98 | 4 / 9 | |
| 0.2.97 | 4 / 9 |
v1.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.133
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.132
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.127
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.