crates.io package intelligence

log — deep security report

ShadowCanopy's full breakdown of log on crates.io: verdict, AI analysis, dependency chain, network behavior, prebuilds, and obfuscated code.

Safe to use
Deep-scanned by ShadowCanopy — no threats found in its code, dependencies, or network behavior.
Scanned 11/3/2026
Approvedlog@0.4.35View on registry ↗latest: 0.4.35

The 'log' crate (0.4.35) is the standard Rust logging facade. The flagged 'f33c::1' IPv6 literal appears only in test/example code that exercises the existing std::net::* value-capture paths (see impl_to_value_from_display for IpAddr/Ipv6Addr). No network sockets, exfiltration, or C2 behavior exists in the supplied source.

Protect your projects free

AI breakdown

Plain-English summary of what this package does and how it behaves.

This package is the 'log' crate (v0.4.35), a standard Rust logging facade that provides macros, traits, and key-value support for application logging without tying to a specific backend.

Capabilities

  • Provides logging macros and levels
  • Supports key-value logging
  • Includes optional serde integration

Data access

  • None observed

Network

  • Hardcoded public IP in network code (ATK-028)

Standard logging library with no dependencies or scripts; the reported hardcoded IP finding warrants code review but is not evidenced in the provided file sample.

Security findings (2)

Static analysis rule matches, with the exact code that triggered them.

highHardcoded public IP in network codeATK-028src/kv/value.rs

File src/kv/value.rs contains a hardcoded public IP (f33c::1) used in network code — review for hidden exfiltration or C2 endpoints.

highHardcoded public IP in network codeATK-028log-0.4.35/src/kv/value.rs

File log-0.4.35/src/kv/value.rs contains a hardcoded public IP (f33c::1) used in network code — review for hidden exfiltration or C2 endpoints.

Files in package (50)

.cargo_vcs_info.jsonlog-0.4.35/.cargo_vcs_info.json.github/workflows/main.ymllog-0.4.35/.github/workflows/main.yml.github/workflows/publish.ymllog-0.4.35/.github/workflows/publish.yml.gitignorelog-0.4.35/.gitignoreCHANGELOG.mdlog-0.4.35/CHANGELOG.mdCargo.locklog-0.4.35/Cargo.lockCargo.tomllog-0.4.35/Cargo.tomlCargo.toml.origlog-0.4.35/Cargo.toml.origLICENSE-APACHElog-0.4.35/LICENSE-APACHELICENSE-MITlog-0.4.35/LICENSE-MITREADME.mdlog-0.4.35/README.mdbenches/value.rslog-0.4.35/benches/value.rsrelease-plz.tomllog-0.4.35/release-plz.tomlsrc/__private_api.rslog-0.4.35/src/__private_api.rssrc/kv/error.rslog-0.4.35/src/kv/error.rssrc/kv/key.rslog-0.4.35/src/kv/key.rssrc/kv/mod.rslog-0.4.35/src/kv/mod.rssrc/kv/source.rslog-0.4.35/src/kv/source.rssrc/kv/value.rslog-0.4.35/src/kv/value.rssrc/lib.rslog-0.4.35/src/lib.rs

How ShadowCanopy checks crates.io packages

ShadowCanopy blocks every dependency by default and only lets through what it can verify — against live malicious-package advisories, an AI behavior scan, and a byte-for-byte hash check. It protects installs across npm, PyPI, crates.io, pkg.go.dev, RubyGems, Maven Central, NuGet, Packagist, Hex, pub.dev, Swift Package Manager.

Protect your projects freeSee what's being blocked

This report reflects ShadowCanopy's threat intelligence at page load and is informational, not a warranty. Canonical URL: https://shadowcanopy.dev/packages/crates/log