| Key | Value |
|---|---|
| FileName | ./usr/lib/node_modules/dep-graph/lib/dep-graph.js |
| FileSize | 3305 |
| MD5 | BFC5701DEAB90DD5D9AB16958B35D486 |
| SHA-1 | 9AF5505C4AB86C1012F70843C8734CD39072D1D6 |
| SHA-256 | 66C5E06CF018CE07FC6DF763889EABCE3D34DAE9FF52E8BBFA4ABBE4416DA71C |
| SSDEEP | 96:MEcGpYpQjCpI8CyNq92FBCQFCaq/ACaqBIXNN4iU1UhZmV2W:MlGpYpQmpPCyNOuCaqoCaqBIXN6iU1aG |
| TLSH | T18C61CC99EEF72053A217B5280B6F6024A337D80F4048D9087B6C06E85FA876445EAFF5 |
| 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 | DEBBA0E76ED2013CF3A32368790DBFD9 |
| 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 | 3.fc20 |
| PackageVersion | 1.1.0 |
| SHA-1 | 93A58CC46F8F4C137D9365561F2361AE920BE4CC |
| SHA-256 | 27C4785460F7EBCCE9FB0C030F5581BD7D7AABDD03E903519D96AB0138260CBF |