Result for 0885B5FFA861E5764EC4328E5E6A67D698B25FDF

Query result

Key Value
FileName./usr/share/gocode/src/golang.org/x/mod/zip/testdata/create_from_dir/bad_gomod_case.txt
FileSize128
MD5DA5626936ADC11AF82CC36B8B80027D7
SHA-10885B5FFA861E5764EC4328E5E6A67D698B25FDF
SHA-2564D3A5CFD867E3EF7937EBDB381A4001A34AA4DB172E0A23D547D937C996CE01D
SSDEEP3:UfVPfvWhTU/SiGXIWQPmBYqLRLV2Jz4zcvII8ayIfAfvn:6dvIGSi7PmOqpVe8Ifgvn
TLSHT15CB09B410FF910251444819C741B54A41E61063849E25C44D89C565E6D0BCC356615DB
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
FileSize79720
MD5D519A1E579495ADFC532CECD63E6E6E6
PackageDescriptionGo module mechanics libraries This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves. . It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages. . The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamegolang-golang-x-mod-dev
PackageSectiondevel
PackageVersion0.2.0-2
SHA-1543D54AE7AFF4B0B4716408210661099B4E62328
SHA-2564C3C21DDEF6F685C9E338571EE88F3B677A70E317460214592B0A198509B5736
Key Value
FileSize79760
MD5774ACDEEB9B475A5F10AB98A1B93FF89
PackageDescriptionGo module mechanics libraries This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves. . It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages. . The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.
PackageMaintainerDebian Go Packaging Team <team+pkg-go@tracker.debian.org>
PackageNamegolang-golang-x-mod-dev
PackageSectiondevel
PackageVersion0.2.0-2~bpo10+1
SHA-133CDCFBD09706CA512761A7D0F1F87C4ACEAE235
SHA-256554CDA9B558484B59775E55717D4C51586589B3700F8B6EA2505040DD5A5A872