Result for 134B454E3AE5A3A375DE7109F2CBD5B86EE1DDC8

Query result

Key Value
CRC32E8DE602A
FileNamesnap-hashlookup-import/vendor/bundle/jruby/1.9/gems/mime-types-2.6.2/support/convert/columnar.rb
FileSize2053
MD50D05DE63289D84D43DD67CDA076B4EBA
OpSystemCode{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode{'ApplicationType': 'Multilanguage', 'Language': '924', 'MfgCode': '599', 'OpSystemCode': ' 2017', 'ProductCode': '183719', 'ProductName': 'SUSE Enterprise Storage 4 x86_64- ', 'ProductVersion': 'dl.Aug.30'}
SHA-1134B454E3AE5A3A375DE7109F2CBD5B86EE1DDC8
SHA-256556750B358F82FB7B3A30656A9244ADFE12DEA4FFC73EB43D0B4452EA5CE2E2D
SHA-5127ACE380F8A937B2E805C8FC00D80A90AEBE76E023ADDDBC87D0E97DE1853F3F7D093EBF492E1E70C8DBFB9CAB420E19B0AC1F416F775F2D71EC4B956D460A658
SSDEEP48:V1eycFaROsBRWUhI/2RvwcoFpvAnMZvLUK21UB3ocW3UF9E/H:BROwc2RvwcoFRxl21se/
SpecialCode
TLSHT19841C02B69D82DA127C3D4656DD9AD030F25B2434E84026073ED82E58F59732E5E3FBA
dbnsrl_modern_rds
insert-timestamp1659223286.781142
mimetypetext/x-ruby
sourcesnap:inHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33
tar:gnameroot
tar:unameroot
hashlookup:parent-total15
hashlookup:trust100

Network graph view

Parents (Total: 15)

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

Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/6.8/packages//amd64//logstash-7.9.1v0.tgz
MD5C4BB5FF05896FD7244FFD31A66BDCF52
SHA-18106B38AD5FC2D2C7DF62C5C5F3AA311BC37DA46
SHA-2562113ED48590BB4D241BCA809944C3E6993E763B674E6C4CC5DE168BFD0D81206
SSDEEP3145728:MtqGBt7zE9HXFCWvpl4HHpgIhFxnncnDWeM2sRNKJ/1CbFfL79:uACWvpl4HHpZHnyERNKJ/1afLh
TLSHT19D7833E028BEB47DA278BF31C56D970432E704D18895FDBAFBC7DB620B815C5856428E
Key Value
MD58056051BC11F3E12168A3DC1FB698CDF
PackageArchx86_64
PackageDescriptionThe 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.
PackageNameruby3.0-rubygem-mime-types
PackageRelease1.43
PackageVersion2.6.1
SHA-14F23309833DF9702D06A66AE9455016A3E0D38F4
SHA-25667FE954E480C84D022C33E0F6A1033F9C784534B60DD39926BA73CAD7B0B90A1
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/6.4/packages//amd64//logstash-6.4.1v0.tgz
MD5E57D3E6EB0F563BE35329579569118EC
SHA-15C655AF47350A3E85E6BE11F97C9E15307B6FC71
SHA-2566AC66146F6DC5CCF44145B0AF7D6E3E0B7AAF1CBFEB5DD3948A50445155CF197
SSDEEP3145728:PM+5s6fw3955WMGBO8473pMIo/1ntEuZcmbOh4Povo1GnmHnvMsDfeh0U:U+5sdT5W7P4DpyvEGlbOhgGnmU2feaU
TLSHT1A57833B864708C1DD7CEF63BF1D39F0C6911A4D88E82E96AF7CAD5B603C2BD406A6154
Key Value
MD589EE1DA600E6450B54FCD4154799329A
PackageArchi586
PackageDescriptionThe 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.
PackageNameruby2.7-rubygem-mime-types
PackageRelease1.44
PackageVersion2.6.1
SHA-1CF07139C74FF6D0AEB82BB688D71C47084E97CA4
SHA-25684B75F779704CBED4DB794A83D8D0E3BB4131BB7ECDB9D9735CBABD22C1FE3C4
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/5.8/packages//amd64//logstash-1.5.3v0.tgz
MD5BD0E90FA699F936381A1187FF8E8C242
SHA-1D61B02FA025D2345167B86F25F6F1E4FF79B6014
SHA-256EFB86850931951615AA62C7A765F34A50AD52BB765081DA6B9103AAFDADC0249
SSDEEP1572864:RKNpccEfTCmcv+Zr00rO/Yp/VBPNlJQqxes/lcSrcBZAJhmrXStQl208M:RLcEfTClgQ8OwpVNnJcV1Z38Qxt
TLSHT17A183333B07BE426E554B27C32A4E36770915DF4A506ED3AFFA960BE4B5B0E2012E543
Key Value
MD5A6627C24CB382405ED34D58088BD4835
PackageArchx86_64
PackageDescriptionThe 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.
PackageNameruby2.7-rubygem-mime-types
PackageRelease1.43
PackageVersion2.6.1
SHA-1065F4F55FCDBFCBC05B36E8C62DE47E16C3F344F
SHA-2568314C8FC75FC85B3A08B542359C49FE009F5153CD75A21A3133977733FB6C0F5
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//amd64//logstash-7.10.0v0.tgz
MD50DA46B8AC1EEE755C58DAE164C48E5E1
SHA-1015C27AABA74A3A39021F1071CBAFC957159B3D3
SHA-256EFFA8BFB169444D6962D50525086E0D090E831F5926EE0415726B67F6FDCCD44
SSDEEP3145728:PfoSDFsHqt7L4BwVF+UIUDu1+eK1Jbf72:PH46gQ+UpufCJbfS
TLSHT1967833A1D1785434E1ADBB30A4CFAB0420BA14D84FE5DC7EF7AF56B61B063C9911CB29
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//amd64//logstash-7.6.2v0.tgz
MD5A310B45DBD5B199A482F2DC2E21BA9F2
SHA-120A2CF27509B9DABDC78F4D48135162D0602777B
SHA-256237B42D46FAA96EEDC4D6C8A2C5B27792ECF674D992EFB779C7AAA20D0904CBB
SSDEEP3145728:E4fSck+CINdy8CWNR+Zyrqe/9q+x7xlyil3lZcZ33aOn/WOD3icse0906pUTPuwr:EOk+CINdXCXyrqd+Xwil3O3aOnR3Dsef
TLSHT1BF8833BCA5E4F8AEC1ACFA74F056476C791724C8CA61DC36F71A01E56B937C8D231628
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/6.5/packages//amd64//logstash-6.6.1p0v0.tgz
MD531793C96D676B585D159FC0584258781
SHA-1E09F37124EF7A43F309E7B6156E4E969FD1A6C1B
SHA-256191952C6B0EEB5BAAD9180D4F162EF28F15ABC4D58C4C7B667DEA377AADDA78B
SSDEEP3145728:VRyMpAYs8RyyuZcA7TRn5KuSX4QFKFicPGSlEtAeYAwxDfeh0S:VRyos8RyygNHauSX4FizSlEtADdfeaS
TLSHT1618833B8B1704C71E25A7F27F1A58BC0966128E88B5EED66FB87D0F52B833C08597513
Key Value
MD5301AF7DB5B6178858EF13503AC5A594A
PackageArchi586
PackageDescriptionThe 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.
PackageNameruby3.0-rubygem-mime-types
PackageRelease1.44
PackageVersion2.6.1
SHA-1C87AD70AE6CCB856990A8E52768195013F05AD15
SHA-256F363B41329F690D10F4109C659448E899AAC917090CC9461474A5970487F5D51
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD/6.6/packages//amd64//logstash-6.6.1p1v0.tgz
MD5305F9F2C903A9F067D377947A129BAF1
SHA-18B7CBB89465F45523553AB5FD2CEE29B32086610
SHA-256E7F10E529341C2532705498CACB7AD676CE8F2F5BB9A0D18E7BB93CCD4BD69F3
SSDEEP3145728:QRyMpAYs8RyyuZcA7TRn5KuSX4QFKFicPGSlEtAeYAwxDfeh0s:QRyos8RyygNHauSX4FizSlEtADdfeas
TLSHT11E8833B8B1704C71E25A7F37B1A58BC0966128E88B5FED66FB87C0B52B837C08657513
Key Value
FileNamehttp://archlinux.mirror.root.lu//pool//community//logstash-7.10.1-1-x86_64.pkg.tar.zst
MD565A39AE61A5D93C6BA60BB63438F8BF0
SHA-19BEEDC6A7BA11272F2F5D55236882B6F843DF748
SHA-25696F0D9BC2C0A5477E9592178A620C5CEAE1F4EBFDE9B9A32202B3CD809C05551
SSDEEP3145728:2bHgq7IIkLUf072CfDBe8Vah55TF962tXcaU/Y4B/ItoY7lrjJ36Y3Xd:2LHIIk772+DvVabZF962tTp23YJJ36Y9
TLSHT18D6833C8BEE6D2DAEF7DC91389D1B5432ECA2E45A70179B1B812F5D233531A1840CDB9
Key Value
MD5548C10308035A27E9490AD11223B7D8B
PackageArchx86_64
PackageDescriptionThe 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.
PackageNameruby2.7-rubygem-mime-types
PackageRelease1.44
PackageVersion2.6.1
SHA-192D23CC5F41D92327884B811D7B205C78FD2300F
SHA-256C21804F36237A06C6DCC16B82F8416EA02E89052780819D6647BEAF2AEF2AC8B
Key Value
MD5F84B0FA42A451178CC5BAC56B621F012
PackageArchx86_64
PackageDescriptionThe 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.
PackageNameruby3.0-rubygem-mime-types
PackageRelease1.44
PackageVersion2.6.1
SHA-1B72E8FBCF6EACBD4B8B582B43AA853603531E92F
SHA-256D6AEFFD078F4ED9AAD66C904B5A60798ED005A2B6930335526910F57C8C1A276
Key Value
SHA-12173C791F83932F667A009E43CD966C3BEF466F0
snap-authoritycanonical
snap-filenameinHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33.snap
snap-idinHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33
snap-namefirewallreports
snap-publisher-idFySbOnFUWsRfJsLzIW1SHQcBZxIb06XE
snap-signkeyBWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp2018-05-16T11:26:27.131756Z
source-urlhttps://api.snapcraft.io/api/v1/snaps/download/inHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33.snap