Parents (Total: 17)

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

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//amd64//logstash-7.10.0v0.tgz
MD5	0DA46B8AC1EEE755C58DAE164C48E5E1
SHA-1	015C27AABA74A3A39021F1071CBAFC957159B3D3
SHA-256	EFFA8BFB169444D6962D50525086E0D090E831F5926EE0415726B67F6FDCCD44
SSDEEP	3145728:PfoSDFsHqt7L4BwVF+UIUDu1+eK1Jbf72:PH46gQ+UpufCJbfS
TLSH	T1967833A1D1785434E1ADBB30A4CFAB0420BA14D84FE5DC7EF7AF56B61B063C9911CB29

Key	Value
FileSize	110564
MD5	0C74CCB436E8FBE3233FBA70B9B9F332
PackageDescription	guess MIME type of files This library allows for the identification of a file's likely MIME content type. The identification of MIME content type is based on a file's filename extensions.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	ruby-mime-types
PackageSection	ruby
PackageVersion	2.6.1-1
SHA-1	04606CB0A3F3DE84DFB314467E7246D451B47468
SHA-256	E1374B3457D413F8FB2565877E21E1B066D0D37EE9666A44331946D3AF0C47C5

Key	Value
MD5	A6627C24CB382405ED34D58088BD4835
PackageArch	x86_64
PackageDescription	The mime-types library provides a library and registry for information about MIME content type definitions. It can be used to determine defined filename extensions for MIME types, or to use filename extensions to look up the likely MIME type definitions. MIME content types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. The mime-types library provides the ability for detailed information about MIME entities (provided as an enumerable collection of MIME::Type objects) to be determined and used. There are many types defined by RFCs and vendors, so the list is long but by definition incomplete; don't hesitate to add additional type definitions. MIME type definitions found in mime-types are from RFCs, W3C recommendations, the {IANA Media Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and user contributions. It conforms to RFCs 2045 and 2231. This is release 2.6 with two new experimental features. The first new feature is a new default registry storage format that greatly reduces the initial memory use of the mime-types library. This feature is enabled by requiring +mime/types/columnar+ instead of +mime/types+ with a small performance cost and no change in *total* memory use if certain methods are called (see {Columnar Store}[#columnar-store] for more details). The second new feature is a logger interface that conforms to the expectations of an ActiveSupport::Logger so that warnings can be written to an application's log rather than the default location for +warn+. This interface may be used for other logging purposes in the future. mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation warnings are no longer cached but provided every time the method is called. mime-types 2.6 supports Ruby 1.9.2 or later.
PackageName	ruby2.7-rubygem-mime-types
PackageRelease	1.43
PackageVersion	2.6.1
SHA-1	065F4F55FCDBFCBC05B36E8C62DE47E16C3F344F
SHA-256	8314C8FC75FC85B3A08B542359C49FE009F5153CD75A21A3133977733FB6C0F5

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//amd64//logstash-7.6.2v0.tgz
MD5	A310B45DBD5B199A482F2DC2E21BA9F2
SHA-1	20A2CF27509B9DABDC78F4D48135162D0602777B
SHA-256	237B42D46FAA96EEDC4D6C8A2C5B27792ECF674D992EFB779C7AAA20D0904CBB
SSDEEP	3145728:E4fSck+CINdy8CWNR+Zyrqe/9q+x7xlyil3lZcZ33aOn/WOD3icse0906pUTPuwr:EOk+CINdXCXyrqd+Xwil3O3aOnR3Dsef
TLSH	T1BF8833BCA5E4F8AEC1ACFA74F056476C791724C8CA61DC36F71A01E56B937C8D231628

Key	Value
SHA-1	2173C791F83932F667A009E43CD966C3BEF466F0
snap-authority	canonical
snap-filename	inHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33.snap
snap-id	inHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33
snap-name	firewallreports
snap-publisher-id	FySbOnFUWsRfJsLzIW1SHQcBZxIb06XE
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2018-05-16T11:26:27.131756Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/inHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33.snap

Key	Value
MD5	8056051BC11F3E12168A3DC1FB698CDF
PackageArch	x86_64
PackageDescription	The mime-types library provides a library and registry for information about MIME content type definitions. It can be used to determine defined filename extensions for MIME types, or to use filename extensions to look up the likely MIME type definitions. MIME content types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. The mime-types library provides the ability for detailed information about MIME entities (provided as an enumerable collection of MIME::Type objects) to be determined and used. There are many types defined by RFCs and vendors, so the list is long but by definition incomplete; don't hesitate to add additional type definitions. MIME type definitions found in mime-types are from RFCs, W3C recommendations, the {IANA Media Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and user contributions. It conforms to RFCs 2045 and 2231. This is release 2.6 with two new experimental features. The first new feature is a new default registry storage format that greatly reduces the initial memory use of the mime-types library. This feature is enabled by requiring +mime/types/columnar+ instead of +mime/types+ with a small performance cost and no change in *total* memory use if certain methods are called (see {Columnar Store}[#columnar-store] for more details). The second new feature is a logger interface that conforms to the expectations of an ActiveSupport::Logger so that warnings can be written to an application's log rather than the default location for +warn+. This interface may be used for other logging purposes in the future. mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation warnings are no longer cached but provided every time the method is called. mime-types 2.6 supports Ruby 1.9.2 or later.
PackageName	ruby3.0-rubygem-mime-types
PackageRelease	1.43
PackageVersion	2.6.1
SHA-1	4F23309833DF9702D06A66AE9455016A3E0D38F4
SHA-256	67FE954E480C84D022C33E0F6A1033F9C784534B60DD39926BA73CAD7B0B90A1

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.4/packages//amd64//logstash-6.4.1v0.tgz
MD5	E57D3E6EB0F563BE35329579569118EC
SHA-1	5C655AF47350A3E85E6BE11F97C9E15307B6FC71
SHA-256	6AC66146F6DC5CCF44145B0AF7D6E3E0B7AAF1CBFEB5DD3948A50445155CF197
SSDEEP	3145728:PM+5s6fw3955WMGBO8473pMIo/1ntEuZcmbOh4Povo1GnmHnvMsDfeh0U:U+5sdT5W7P4DpyvEGlbOhgGnmU2feaU
TLSH	T1A57833B864708C1DD7CEF63BF1D39F0C6911A4D88E82E96AF7CAD5B603C2BD406A6154

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.8/packages//amd64//logstash-7.9.1v0.tgz
MD5	C4BB5FF05896FD7244FFD31A66BDCF52
SHA-1	8106B38AD5FC2D2C7DF62C5C5F3AA311BC37DA46
SHA-256	2113ED48590BB4D241BCA809944C3E6993E763B674E6C4CC5DE168BFD0D81206
SSDEEP	3145728:MtqGBt7zE9HXFCWvpl4HHpgIhFxnncnDWeM2sRNKJ/1CbFfL79:uACWvpl4HHpZHnyERNKJ/1afLh
TLSH	T19D7833E028BEB47DA278BF31C56D970432E704D18895FDBAFBC7DB620B815C5856428E

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.6/packages//amd64//logstash-6.6.1p1v0.tgz
MD5	305F9F2C903A9F067D377947A129BAF1
SHA-1	8B7CBB89465F45523553AB5FD2CEE29B32086610
SHA-256	E7F10E529341C2532705498CACB7AD676CE8F2F5BB9A0D18E7BB93CCD4BD69F3
SSDEEP	3145728:QRyMpAYs8RyyuZcA7TRn5KuSX4QFKFicPGSlEtAeYAwxDfeh0s:QRyos8RyygNHauSX4FizSlEtADdfeas
TLSH	T11E8833B8B1704C71E25A7F37B1A58BC0966128E88B5FED66FB87C0B52B837C08657513

Key	Value
MD5	548C10308035A27E9490AD11223B7D8B
PackageArch	x86_64
PackageDescription	The mime-types library provides a library and registry for information about MIME content type definitions. It can be used to determine defined filename extensions for MIME types, or to use filename extensions to look up the likely MIME type definitions. MIME content types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. The mime-types library provides the ability for detailed information about MIME entities (provided as an enumerable collection of MIME::Type objects) to be determined and used. There are many types defined by RFCs and vendors, so the list is long but by definition incomplete; don't hesitate to add additional type definitions. MIME type definitions found in mime-types are from RFCs, W3C recommendations, the {IANA Media Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and user contributions. It conforms to RFCs 2045 and 2231. This is release 2.6 with two new experimental features. The first new feature is a new default registry storage format that greatly reduces the initial memory use of the mime-types library. This feature is enabled by requiring +mime/types/columnar+ instead of +mime/types+ with a small performance cost and no change in *total* memory use if certain methods are called (see {Columnar Store}[#columnar-store] for more details). The second new feature is a logger interface that conforms to the expectations of an ActiveSupport::Logger so that warnings can be written to an application's log rather than the default location for +warn+. This interface may be used for other logging purposes in the future. mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation warnings are no longer cached but provided every time the method is called. mime-types 2.6 supports Ruby 1.9.2 or later.
PackageName	ruby2.7-rubygem-mime-types
PackageRelease	1.44
PackageVersion	2.6.1
SHA-1	92D23CC5F41D92327884B811D7B205C78FD2300F
SHA-256	C21804F36237A06C6DCC16B82F8416EA02E89052780819D6647BEAF2AEF2AC8B