@xylabs/events
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is the sanctioned successor package per deprecation notice, not an unrelated third party. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher matched as known maintainer by email; benign org handoff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org account rotation, not takeover; provenance direction unchanged. | ai | |
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer, no behavior change in diff. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Deprecated shim redirecting to @ariestools/sdk; size drop is structural, not code replacement. | ai | |
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): LGPL-3.0-only is the declared license for this package family; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): XYOracleNetwork monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 31 of 131)
| Version | Deps | Published |
|---|---|---|
| 5.0.30 | 7 / 6 | |
| 5.0.29 | 7 / 6 | |
| 5.0.28 | 7 / 6 | |
| 5.0.27 | 7 / 6 | |
| 5.0.26 | 7 / 6 | |
| 5.0.25 | 7 / 6 | |
| 5.0.24 | 7 / 6 | |
| 5.0.23 | 7 / 6 | |
| 5.0.22 | 7 / 6 | |
| 5.0.21 | 7 / 6 | |
| 5.0.20 | 7 / 6 | |
| 5.0.19 | 7 / 6 | |
| 5.0.18 | 7 / 6 | |
| 5.0.17 | 7 / 6 | |
| 5.0.16 | 7 / 6 | |
| 5.0.15 | 7 / 6 | |
| 5.0.14 | 7 / 6 | |
| 5.0.13 | 7 / 6 | |
| 5.0.12 | 7 / 6 | |
| 5.0.11 | 7 / 6 | |
| 5.0.10 | 7 / 6 | |
| 5.0.9 | 7 / 6 | |
| 5.0.8 | 7 / 6 | |
| 5.0.7 | 7 / 6 | |
| 5.0.6 | 7 / 6 | |
| 5.0.5 | 7 / 6 | |
| 5.0.4 | 7 / 6 | |
| 5.0.3 | 7 / 6 | |
| 5.0.2 | 7 / 6 | |
| 5.0.1 | 7 / 6 | |
| 5.0.0 | 7 / 6 |
v5.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.