@xylabs/logger
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): High-volume publisher with strong approval history; likely a CI pipeline change, not a supply-chain indicator. | ai | |
| dependencies | unvetted-dep:@xylabs/error | AI (dependencies): Same-org sibling dep from xylabs monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@xylabs/typeof | AI (dependencies): Same-org sibling dep from xylabs monorepo; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Long-established xylabs package; lack of provenance is consistent across their entire SDK release history. | ai |
Versions (showing 18 of 119)
| Version | Deps | Published |
|---|---|---|
| 5.0.17 | 3 / 5 | |
| 5.0.16 | 3 / 5 | |
| 5.0.15 | 3 / 5 | |
| 5.0.14 | 3 / 5 | |
| 5.0.13 | 3 / 5 | |
| 5.0.12 | 3 / 5 | |
| 5.0.11 | 3 / 5 | |
| 5.0.10 | 3 / 5 | |
| 5.0.9 | 3 / 5 | |
| 5.0.8 | 3 / 5 | |
| 5.0.7 | 3 / 5 | |
| 5.0.6 | 3 / 5 | |
| 5.0.5 | 3 / 5 | |
| 5.0.4 | 3 / 5 | |
| 5.0.3 | 3 / 5 | |
| 5.0.2 | 3 / 5 | |
| 5.0.1 | 3 / 5 | |
| 5.0.0 | 3 / 5 |
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.14
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.13
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.12
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.11
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.5
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.2
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.1
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.