← Home

@dot/log

A beautiful and minimal logger for all applications

8
Versions
MPL-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

shellscape

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:glob AI (typosquat): @dot/log is a scoped logger package by established publisher shellscape; Levenshtein match to 'glob' is coincidental due to short name length. ai
typosquat typosquat.levenshtein:koa AI (typosquat): @dot/log is a scoped logger package by established publisher shellscape; Levenshtein match to 'koa' is coincidental due to short name length. ai
typosquat typosquat.levenshtein:got AI (typosquat): @dot/log is a scoped logger package by established publisher shellscape; Levenshtein match to 'got' is coincidental due to short name length. ai
typosquat typosquat.levenshtein:pg AI (typosquat): @dot/log is a scoped logger package by established publisher shellscape; Levenshtein match to 'pg' is coincidental due to short name length. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @dot/log is a scoped logger package by established publisher shellscape; Levenshtein match to 'joi' is coincidental due to short name length. ai
typosquat typosquat.levenshtein:zod AI (typosquat): @dot/log is a scoped logger package by established publisher shellscape; Levenshtein match to 'zod' is coincidental due to short name length. ai

Versions (showing 8 of 8)

Version Deps Published
0.2.1 3 / 0
0.2.0 3 / 0
0.1.5 3 / 0
0.1.4 3 / 0
0.1.3 3 / 0
0.1.2 3 / 0
0.1.1 3 / 0
0.1.0 3 / 0

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

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.