js-logger
Lightweight, unobtrusive, configurable JavaScript logger
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:test-src/vendor/sinon-1.10.3.js | AI (source-diff): This is the well-known Sinon.JS 1.10.3 test mocking library vendored under test-src/vendor/. XHR faking and dynamic function wrapping are core Sinon features, not malware. False positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change (calaniz → jonnyreeves) occurred in 2014 and reflects a legitimate account transition; jonnyreeves is the documented author with matching GitHub repo and strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jonnyreeves is the documented author of js-logger; maintainer addition reflects legitimate ownership, not a takeover. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is fully explained by addition of qunit-1.14.0.js (61KB) in the test vendor directory — a known testing library, not a payload. | ai | |
| source-diff | net-exec-file:test-src/vendor/sinon-1.14.1.js | AI (source-diff): Sinon.JS 1.14.1 vendored into test-src/vendor/ is a well-known BSD-licensed test mocking library. Network/exec patterns are its XHR-faking and spy features, not malware. Not a runtime dependency. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process.spawn in gulpfile.js is standard build tooling usage, not runtime code. Stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 0 / 9 | |
| 1.6.0 | 0 / 7 | |
| 1.5.0 | 0 / 9 | |
| 1.4.1 | 0 / 9 | |
| 1.4.0 | 0 / 9 | |
| 1.3.0 | 0 / 9 | |
| 1.2.0 | 0 / 9 | |
| 1.1.1 | 0 / 9 | |
| 1.1.0 | 0 / 9 | |
| 1.0.0 | 0 / 9 | |
| 0.9.14 | 0 / 9 | |
| 0.9.13 | 0 / 9 | |
| 0.9.12 | 0 / 9 | |
| 0.9.10 | 0 / 9 | |
| 0.9.9 | 0 / 9 | |
| 0.9.6 | 0 / 9 | |
| 0.9.5 | 0 / 9 | |
| 0.1.0 | 0 / 0 |
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
2 findingsThis version was published by a different npm account than previous versions on 2014-07-12. 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.
v0.9.9
2 findingsThis version was published by a different npm account than previous versions on 2014-07-12. 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.
v0.9.6
2 findingsThis version was published by a different npm account than previous versions on 2014-05-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.
v0.9.5
2 findingsThis version was published by a different npm account than previous versions on 2014-05-19. 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.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.