@reyaxyz/athena-logger
<p align="center"> Athena Logger sdk for the Reya Network </p>
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@reyaxyz/common | AI (dependencies): Same-org scoped dependency (@reyaxyz); stable pattern across versions of this package. | ai | |
| phantom-deps | phantom-dep:@reyaxyz/common | AI (phantom-deps): Same-org scoped dep from the same monorepo; declared-but-not-directly-imported is a stable false positive for this package. | ai |
Versions (showing 100 of 425)
| Version | Deps | Published |
|---|---|---|
| 0.4.286 | 1 / 2 | |
| 0.4.285 | 1 / 2 | |
| 0.4.284 | 1 / 2 | |
| 0.4.283 | 1 / 2 | |
| 0.4.282 | 1 / 2 | |
| 0.4.281 | 1 / 2 | |
| 0.4.280 | 1 / 2 | |
| 0.4.279 | 1 / 2 | |
| 0.4.278 | 1 / 2 | |
| 0.4.277 | 1 / 2 | |
| 0.4.276 | 1 / 2 | |
| 0.4.275 | 1 / 2 | |
| 0.4.274 | 1 / 2 | |
| 0.4.273 | 1 / 2 | |
| 0.4.272 | 1 / 2 | |
| 0.4.271 | 1 / 2 | |
| 0.4.270 | 1 / 2 | |
| 0.4.269 | 1 / 2 | |
| 0.4.268 | 1 / 2 | |
| 0.4.267 | 1 / 2 | |
| 0.4.266 | 1 / 2 | |
| 0.4.265 | 1 / 2 | |
| 0.4.264 | 1 / 2 | |
| 0.4.263 | 1 / 2 | |
| 0.4.262 | 1 / 2 | |
| 0.4.261 | 1 / 2 | |
| 0.4.260 | 1 / 2 | |
| 0.4.259 | 1 / 2 | |
| 0.4.258 | 1 / 2 | |
| 0.4.257 | 1 / 2 | |
| 0.4.256 | 1 / 2 | |
| 0.4.255 | 1 / 2 | |
| 0.4.254 | 1 / 2 | |
| 0.4.253 | 1 / 2 | |
| 0.4.252 | 1 / 2 | |
| 0.4.251 | 1 / 2 | |
| 0.4.250 | 1 / 2 | |
| 0.4.249 | 1 / 2 | |
| 0.4.248 | 1 / 2 | |
| 0.4.247 | 1 / 2 | |
| 0.4.246 | 1 / 2 | |
| 0.4.245 | 1 / 2 | |
| 0.4.244 | 1 / 2 | |
| 0.4.243 | 1 / 2 | |
| 0.4.242 | 1 / 2 | |
| 0.4.241 | 1 / 2 | |
| 0.4.240 | 1 / 2 | |
| 0.4.239 | 1 / 2 | |
| 0.4.238 | 1 / 2 | |
| 0.4.237 | 1 / 2 | |
| 0.4.236 | 1 / 2 | |
| 0.4.235 | 1 / 2 | |
| 0.4.234 | 1 / 2 | |
| 0.4.233 | 1 / 2 | |
| 0.4.232 | 1 / 2 | |
| 0.4.231 | 1 / 2 | |
| 0.4.230 | 1 / 2 | |
| 0.4.229 | 1 / 2 | |
| 0.4.228 | 1 / 2 | |
| 0.4.227 | 1 / 2 | |
| 0.4.226 | 1 / 2 | |
| 0.4.225 | 1 / 2 | |
| 0.4.224 | 1 / 2 | |
| 0.4.223 | 1 / 2 | |
| 0.4.222 | 1 / 2 | |
| 0.4.221 | 1 / 2 | |
| 0.4.220 | 1 / 2 | |
| 0.4.219 | 1 / 2 | |
| 0.4.218 | 1 / 2 | |
| 0.4.217 | 1 / 2 | |
| 0.4.216 | 1 / 2 | |
| 0.4.215 | 1 / 2 | |
| 0.4.214 | 1 / 2 | |
| 0.4.213 | 1 / 2 | |
| 0.4.212 | 1 / 2 | |
| 0.4.211 | 1 / 2 | |
| 0.4.210 | 1 / 2 | |
| 0.4.209 | 1 / 2 | |
| 0.4.208 | 1 / 2 | |
| 0.4.207 | 1 / 2 | |
| 0.4.206 | 1 / 2 | |
| 0.4.205 | 1 / 2 | |
| 0.4.204 | 1 / 2 | |
| 0.4.203 | 1 / 2 | |
| 0.4.202 | 1 / 2 | |
| 0.4.201 | 1 / 2 | |
| 0.4.200 | 1 / 2 | |
| 0.4.199 | 1 / 2 | |
| 0.4.198 | 1 / 2 | |
| 0.4.197 | 1 / 2 | |
| 0.4.196 | 1 / 2 | |
| 0.4.195 | 1 / 2 | |
| 0.4.194 | 1 / 2 | |
| 0.4.193 | 1 / 2 | |
| 0.4.192 | 1 / 2 | |
| 0.4.191 | 1 / 2 | |
| 0.4.190 | 1 / 2 | |
| 0.4.189 | 1 / 2 | |
| 0.4.188 | 1 / 2 | |
| 0.4.187 | 1 / 2 |
v0.4.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.208
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.204
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.190
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.