logging
Lightweight informative modern console logging.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package by a trusted maintainer with a long clean history; lack of Sigstore provenance is a best-practice gap, not a security risk for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 3 / 13 | |
| 4.0.0 | 3 / 13 | |
| 3.3.0 | 3 / 21 | |
| 3.2.0 | 3 / 21 | |
| 3.1.1 | 3 / 21 | |
| 3.1.0 | 3 / 21 | |
| 3.0.0 | 3 / 21 | |
| 2.0.21 | 0 / 1 | |
| 2.0.20 | 0 / 1 | |
| 2.0.19 | 0 / 1 | |
| 2.0.18 | 0 / 1 | |
| 2.0.16 | 0 / 1 | |
| 2.0.15 | 0 / 1 | |
| 2.0.14 | 0 / 1 | |
| 2.0.13 | 0 / 1 | |
| 2.0.12 | 0 / 0 | |
| 2.0.11 | 0 / 0 | |
| 2.0.10 | 0 / 0 | |
| 2.0.9 | 0 / 0 | |
| 2.0.8 | 0 / 0 | |
| 2.0.6 | 0 / 0 | |
| 2.0.4 | 0 / 0 | |
| 2.0.3 | 0 / 0 | |
| 2.0.2 | 0 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 0.0.0 | 0 / 0 |
v4.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dylang.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dylang.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dylang.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.