npmlog
logger for npm
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 | publisher-changed | AI (provenance): lukekarrys is a known npm/GitHub Inc. team member; the gar→lukekarrys transition is a documented legitimate maintainer change within the npm CLI team. | ai | |
| bogus-package | bogus-package | AI (bogus-package): isaacs is Isaac Z. Schlueter, npm's creator — flagging him as spam is a false positive. npmlog is the official npm logger under the npm GitHub org. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 7.0.1 | 4 / 3 | |
| 7.0.0 | 4 / 3 | |
| 6.0.2 | 4 / 3 | |
| 6.0.1 | 4 / 2 | |
| 6.0.0 | 4 / 2 | |
| 5.0.1 | 4 / 2 | |
| 5.0.0 | 4 / 2 | |
| 4.1.2 | 4 / 2 | |
| 4.1.1 | 4 / 2 | |
| 4.1.0 | 4 / 2 | |
| 4.0.2 | 4 / 2 | |
| 4.0.1 | 4 / 2 | |
| 4.0.0 | 4 / 2 | |
| 3.1.2 | 4 / 2 | |
| 3.1.1 | 4 / 2 | |
| 3.1.0 | 4 / 2 | |
| 3.0.0 | 4 / 1 | |
| 2.0.4 | 3 / 1 | |
| 2.0.3 | 3 / 1 | |
| 2.0.2 | 3 / 1 | |
| 2.0.1 | 3 / 1 | |
| 2.0.0 | 3 / 1 | |
| 1.2.1 | 3 / 1 | |
| 1.2.0 | 3 / 1 | |
| 1.1.0 | 3 / 1 | |
| 1.0.0 | 3 / 1 | |
| 0.1.1 | 1 / 1 | |
| 0.1.0 | 1 / 1 | |
| 0.0.6 | 1 / 1 | |
| 0.0.5 | 1 / 1 | |
| 0.0.4 | 1 / 1 | |
| 0.0.3 | 1 / 1 | |
| 0.0.2 | 1 / 1 | |
| 0.0.1 | 1 / 1 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
2 findingsThis version was published by a different npm account than previous versions on 2022-04-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsMaintainer email '[email protected]' uses domain 'aoaioxxysz.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.