tracer
A powerful and customizable logging library for node.js. support color console with timestamp, line number, method name, file name and call stack. you can set transport to file, stream, database(ex: mongodb and clouddb, simpledb). keywords: log, logger, t
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:example/express/node_modules/acorn/src/identifier.js | AI (source-diff): File is a legitimate acorn parser source; long lines are Unicode character class regexes for identifier parsing, not obfuscation. Located in vendored example dependencies. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are vendored node_modules inside the example/express directory, not injected library code. Stable false positive for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is entirely due to vendored example/express/node_modules dependencies. Not a payload injection. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in lib/console.js is a documented tracer feature allowing module-name transport configuration strings. Intentional API design. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval("require") pattern in lib/console.js is used to dynamically load user-specified transport modules; input is a module name string from user config, not remote data. Stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process import in lib/dailyfile.js is consistent with a logging library's file rotation functionality. No evidence of malicious command execution. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 4 / 12 | |
| 1.2.0 | 4 / 12 | |
| 1.1.6 | 4 / 9 | |
| 1.1.5 | 4 / 8 | |
| 1.1.4 | 4 / 8 | |
| 1.1.3 | 4 / 8 | |
| 1.1.2 | 4 / 8 | |
| 1.1.1 | 4 / 8 | |
| 1.1.0 | 4 / 8 | |
| 1.0.3 | 5 / 7 | |
| 1.0.2 | 5 / 7 | |
| 1.0.1 | 5 / 7 | |
| 1.0.0 | 5 / 7 | |
| 0.9.9 | 5 / 7 | |
| 0.9.8 | 4 / 8 | |
| 0.9.6 | 4 / 8 | |
| 0.9.5 | 4 / 8 | |
| 0.9.4 | 4 / 8 | |
| 0.9.3 | 4 / 8 | |
| 0.9.2 | 4 / 6 | |
| 0.9.1 | 4 / 6 | |
| 0.9.0 | 4 / 6 | |
| 0.8.15 | 4 / 6 | |
| 0.8.12 | 4 / 5 | |
| 0.8.11 | 3 / 5 | |
| 0.8.9 | 3 / 5 | |
| 0.8.8 | 3 / 5 | |
| 0.8.7 | 3 / 5 | |
| 0.8.6 | 3 / 5 | |
| 0.8.5 | 3 / 5 | |
| 0.8.3 | 3 / 4 | |
| 0.8.2 | 3 / 3 | |
| 0.8.1 | 3 / 3 | |
| 0.8.0 | 3 / 3 | |
| 0.7.4 | 3 / 3 | |
| 0.7.3 | 3 / 3 | |
| 0.7.2 | 3 / 3 | |
| 0.7.1 | 3 / 2 | |
| 0.7.0 | 3 / 2 | |
| 0.6.2 | 3 / 2 | |
| 0.6.1 | 3 / 2 | |
| 0.6.0 | 3 / 2 | |
| 0.5.1 | 3 / 2 | |
| 0.5.0 | 3 / 2 | |
| 0.4.2 | 3 / 2 | |
| 0.4.1 | 3 / 2 | |
| 0.4.0 | 3 / 2 | |
| 0.3.5 | 3 / 2 | |
| 0.3.4 | 3 / 2 | |
| 0.3.3 | 2 / 2 | |
| 0.3.1 | 2 / 2 |
v1.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: baryon.
Package 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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.