Result for 13D368E19D7B899AE70060F92091E45638BE909E

Query result

Key Value
FileName./usr/share/gocode/src/go.uber.org/zap/zapcore/json_encoder.go
FileSize14589
MD5441138A7E18DD32C4AC869E29BC5FBB4
SHA-113D368E19D7B899AE70060F92091E45638BE909E
SHA-256FE923D6B465320869B12C93510D2190D62DFC202FBC8FFDB5661A25ED3D120C4
SSDEEP384:HwYHFUCwjPqEeYf29Z1TuvMEh2RzD4LCWD6kaNgFEnsvZ7lz68MD8M02S3RzGl08:pHFUCwWw+9Z1TuvMEh2RzD4LCs6kPCOe
TLSHT149625440A994D51BCDC936701891A9F961FCFDE50DD0359AB8EC37EEA305A8B86330F6
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD53F874FAAB3DF62EA9055B57CBA79CB49
PackageArchnoarch
PackageDescriptionPackage Zap provides fast, structured, leveled logging. For applications that log in the hot path, reflection-based serialization and string formatting are prohibitively expensive - they're CPU-intensive and make many small allocations. Put differently, using json.Marshal and fmt.Fprintf to log tons of interface{} makes your application slow. Zap takes a different approach. It includes a reflection-free, zero-allocation JSON encoder, and the base Logger strives to avoid serialization overhead and allocations wherever possible. By building the high-level SugaredLogger on that foundation, zap lets users choose when they need to count every allocation and when they'd prefer a more familiar, loosely typed API. This package contains the source code needed for building packages that reference the following Go import paths: – go.uber.org/zap
PackageMaintainerFedora Project
PackageNamegolang-uber-zap-devel
PackageRelease1.fc32~bootstrap
PackageVersion1.13.0
SHA-11F97DE2C352A35F31A46DE604C45B6203E98F110
SHA-25658ACC78A47AEDE8DA8783024D0F857EF360AA72C047BDF5DB6CC1B4575682B28