← Home

@purinton/log

npm Repository Homepage
11
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rpurinton

Keywords

loggingloggernodejsdebuggingconsolelogwinston

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:glob AI (typosquat): Scoped logging package; Levenshtein match to 'glob' is a false positive. ai
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped logging package; Levenshtein match to 'koa' is a false positive. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped logging package; Levenshtein match to 'got' is a false positive. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped logging package; Levenshtein match to 'pg' is a false positive. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped logging package; Levenshtein match to 'joi' is a false positive. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped logging package; Levenshtein match to 'zod' is a false positive. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.12 1 / 1
1.0.11 1 / 1
1.0.10 1 / 1
1.0.9 1 / 1
1.0.8 1 / 1
1.0.7 1 / 1
1.0.6 1 / 1
1.0.5 1 / 1
1.0.3 1 / 1
1.0.2 1 / 1
1.0.1 1 / 1

v1.0.12

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.

v1.0.11

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.

v1.0.10

1 finding
LOW No provenance attestation provenance

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

v1.0.9

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.

v1.0.8

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.

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.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.

v1.0.1

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.