@dxos/log MIT 32 versions

@dxos/log

npm Repository Homepage

Logger

32

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

richburdonmarik_dwittjosiahdxos-botmykola-vrmchk

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): dxos-bot → GitHub Actions is a CI pipeline migration; SLSA attestation confirms legitimate automated publishing.	ai	2026/06/19
maintainer-change	maintainer-removed	AI (maintainer-change): Consistent with org-level CI migration away from individual maintainer accounts; SLSA provenance corroborates legitimacy.	ai	2026/06/19
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped @dxos package; Levenshtein match to unscoped packages is a false positive for this namespace.	ai	2026/05/29
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped @dxos package; Levenshtein match to unscoped packages is a false positive for this namespace.	ai	2026/05/29
typosquat	typosquat.levenshtein:glob	AI (typosquat): Scoped @dxos package; Levenshtein match to unscoped packages is a false positive for this namespace.	ai	2026/05/29
typosquat	typosquat.levenshtein:zod	AI (typosquat): Scoped @dxos package; Levenshtein match to unscoped packages is a false positive for this namespace.	ai	2026/05/29
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @dxos package; Levenshtein match to unscoped packages is a false positive for this namespace.	ai	2026/05/29
typosquat	typosquat.levenshtein:koa	AI (typosquat): Scoped @dxos package; Levenshtein match to unscoped packages is a false positive for this namespace.	ai	2026/05/29

Versions (showing 32 of 32)

Version	Deps	Published
0.10.0	5 / 2	2026-07-02
0.9.0	5 / 2	2026-06-15
0.8.3	6 / 3	2025-07-03
0.8.2	6 / 3	2025-06-17
0.8.1	6 / 3	2025-04-30
0.8.0	6 / 3	2025-03-15
0.7.4	6 / 3	2024-12-19
0.7.3	6 / 3	2024-12-16
0.7.2	6 / 3	2024-12-05
0.7.1	6 / 3	2024-11-26
0.7.0	6 / 3	2024-11-21
0.6.13	6 / 8	2024-10-22
0.6.12	6 / 8	2024-10-16
0.6.11	6 / 8	2024-09-23
0.6.10	6 / 8	2024-09-18
0.6.9	6 / 8	2024-09-06
0.6.8	6 / 8	2024-09-05
0.6.7	8 / 10	2024-08-26
0.6.6	8 / 10	2024-08-22
0.6.5	8 / 10	2024-08-12
0.6.4	8 / 10	2024-08-02
0.6.3	8 / 10	2024-07-26
0.6.2	8 / 10	2024-07-16
0.6.1	8 / 10	2024-07-11
0.6.0	8 / 10	2024-07-04
0.5.8	8 / 10	2024-06-14
0.5.7	8 / 10	2024-06-12
0.5.6	8 / 10	2024-06-11
0.5.5	8 / 10	2024-05-30
0.5.4	8 / 10	2024-05-29
0.5.3	8 / 10	2024-05-28
0.5.2	8 / 10	2024-05-17

v0.10.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.13

1 finding

LOW No provenance attestation provenance

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

v0.6.12

1 finding

LOW No provenance attestation provenance

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

v0.6.11

1 finding

LOW No provenance attestation provenance

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

v0.6.10

1 finding

LOW No provenance attestation provenance

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

v0.6.9

1 finding

LOW No provenance attestation provenance

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

v0.6.8

1 finding

LOW No provenance attestation provenance

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

v0.6.7

1 finding

LOW No provenance attestation provenance

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

v0.6.6

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

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.5.2

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.