Result for 06B94FCBC17D88DB0828687206F0A0C3CFAE024E

Query result

Key Value
FileName./usr/share/gems/gems/apipie-rails-0.5.5/lib/apipie/errors.rb
FileSize1019
MD524754D2FEECF9D315F200AB606F2C66D
SHA-106B94FCBC17D88DB0828687206F0A0C3CFAE024E
SHA-256F70D232EF211C51F13D7F4004C587155551685940F568F4B4849962A5E201A39
SSDEEP24:pG0VWOGWp3LnGwSXHBXHGXHf/JXH//bdQVXWOGRylqHq0OOI:UXitiP5of/h//bBJclqHqnv
TLSHT15A11EF1FEB530AF702E2A192107039A64FA59623B78044B138DD4FD11FAE852ECB33A1
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
MD5E341B4E1AFF93060D52FFF3425DB976E
PackageArchnoarch
PackageDescriptionApipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead of traditional use of #comments, Apipie lets you describe the code, through the code. This brings advantages like: * No need to learn yet another syntax, you already know Ruby, right? * Possibility of reusing the docs for other purposes (such as validation) * Easier to extend and maintain (no string parsing involved) * Possibility of reusing other sources for documentation purposes (such as routes etc.) The documentation is available from within your app (by default under the /apipie path.) In development mode, you can see the changes as you go. It's markup language agnostic, and even provides an API for reusing the documentation data in JSON.
PackageMaintainerFedora Project
PackageNamerubygem-apipie-rails
PackageRelease8.fc33
PackageVersion0.5.5
SHA-13D290D15D65E331D3A5CEAE44906420320329C95
SHA-2560790B493CC629E46BDC5990AF99F0AF5A5AD4C5C80C8479FBBD7F059554D6B53
Key Value
MD5407565F366765C782F1019CB5CC9EB73
PackageArchnoarch
PackageDescriptionApipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead of traditional use of #comments, Apipie lets you describe the code, through the code. This brings advantages like: * No need to learn yet another syntax, you already know Ruby, right? * Possibility of reusing the docs for other purposes (such as validation) * Easier to extend and maintain (no string parsing involved) * Possibility of reusing other sources for documentation purposes (such as routes etc.) The documentation is available from within your app (by default under the /apipie path.) In development mode, you can see the changes as you go. It's markup language agnostic, and even provides an API for reusing the documentation data in JSON.
PackageMaintainerFedora Project
PackageNamerubygem-apipie-rails
PackageRelease6.fc32
PackageVersion0.5.5
SHA-194C2F67CDE3C39A30DB116DF163E710A021B3708
SHA-256041965137A342A5AFEEF79AF8C14CF7B7968519A4A7E45E9CA3431C4B78D8A26