| Key | Value |
|---|---|
| FileName | ./usr/lib/node_modules/dep-graph/package.json |
| FileSize | 554 |
| MD5 | 1752F0C02715BC1E40B5340D4A936D58 |
| SHA-1 | EF63FC4F87ACEC6ABC3BCD701067DF44F849484E |
| SHA-256 | 56CBAC3B82592CE6D92A5AE4B41ACE38392051672296A06CC7919BBAB0885753 |
| SSDEEP | 12:X67FpGto14WEk5ZLWF2k5P+zCiFYmZxIegdKA:6pf1Hu+6Xe4KA |
| TLSH | T162F02478CA186E63199EB5D1ACAA0013A651445B4C48BC0CF65C430CCF1D4EFE1BC71C |
| hashlookup:parent-total | 1 |
| hashlookup:trust | 55 |
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 |
|---|---|
| MD5 | 4143AE5C4BC4689E08CC0B71AF27B925 |
| PackageArch | noarch |
| PackageDescription | This is a Node.js module for simple dependency graph management in JavaScript. Say you have a set of resources that depend on each other in some way. These resources can be anything (eg, files, chains of command etc.). All that matters is that each one has a unique string identifier, and a list of direct dependencies. dep-graph makes it easy to compute "chains" of dependencies, with guaranteed logical ordering and no duplicates. That's trivial in most cases, but if A depends on B and B depends on A, a naïve dependency graph would get trapped in an infinite loop. dep-graph throws an error if any such "cycles" are detected. |
| PackageMaintainer | Fedora Project |
| PackageName | nodejs-dep-graph |
| PackageRelease | 17.fc32 |
| PackageVersion | 1.1.0 |
| SHA-1 | 04A43AE31D9018C71CF671250B839FB7EAEDF966 |
| SHA-256 | DA31F2835EC8DBC187284530E22F84A5B19D24A1492EEE710950E612E4CC142A |