Result for 0854F20AAFCE25BC85B1110073D495C68CAC577B

Query result

Key Value
FileName./usr/lib/node_modules/winston/package.json
FileSize1025
MD5A1AE9FD6F0C61F51CFEFF00BA1B73175
SHA-10854F20AAFCE25BC85B1110073D495C68CAC577B
SHA-256561FCF6C0AD16E6A391E2EDABBB3F4673E05EBA4860B494DC168AF673D8BAA84
SSDEEP24:TrknLNfLS1Vpx1EueXcX/9BeZfqXa5kd2bHA:TIJfLSjhzBKuEU
TLSHT1FA112957C5E85DAB16CEB6CD98784D86F113D00B8888CD0F36BC419C8F4C7B6048C659
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
MD5EEAA103D1DAA147E19CFFE3B6CAA06C9
PackageArchnoarch
PackageDescriptionThis module is a multiple transport asynchronous logging library for Node.js. Winston is designed to be a simple and universal logging library with support for multiple transports. A transport is essentially a storage device for your logs. Each instance of a winston logger can have multiple transports configured at different levels. For example, one may want error logs to be stored in a persistent remote location (like a database), but all logs output to the console or a local file. There also seemed to be a lot of logging libraries out there that coupled their implementation of logging (ie, how the logs are stored/indexed) to the API that they exposed to the programmer. This library aims to decouple those parts of the process to make it more flexible and extensible.
PackageMaintainerFedora Project
PackageNamenodejs-winston
PackageRelease1.el7
PackageVersion0.7.3
SHA-152A4C86D30125716D2FCD565B05521FA35116D10
SHA-256AC9A3A91A148144C6187E8B70DD8E09C24DCC3BEDA12F50D206ACA9253A6D7E5
Key Value
MD575171B6E08175E16AE88F72F8DBD9D7D
PackageArchnoarch
PackageDescriptionThis module is a multiple transport asynchronous logging library for Node.js. Winston is designed to be a simple and universal logging library with support for multiple transports. A transport is essentially a storage device for your logs. Each instance of a winston logger can have multiple transports configured at different levels. For example, one may want error logs to be stored in a persistent remote location (like a database), but all logs output to the console or a local file. There also seemed to be a lot of logging libraries out there that coupled their implementation of logging (ie, how the logs are stored/indexed) to the API that they exposed to the programmer. This library aims to decouple those parts of the process to make it more flexible and extensible.
PackageMaintainerFedora Project
PackageNamenodejs-winston
PackageRelease1.el6
PackageVersion0.7.3
SHA-199B3156DDF362E2F3727F52705DB412CC7EBF571
SHA-256531B336BCEEC0272AC2AB25C0C49404506AC74C3BA1482DD28AE671D16611C03