Result for 1EB2B0F295CEDF62781FBC8BEAE5804E9DE16C9D

Query result

Key Value
FileName./usr/share/gems/specifications/apipie-rails-0.5.5.gemspec
FileSize1873
MD56FD39B9EAF08D3125D9B8975A42E1BE7
SHA-11EB2B0F295CEDF62781FBC8BEAE5804E9DE16C9D
SHA-256F597FA6940E7A0F3BC24A189B7D7A975B2E37C40582A270D9D7725FD5AE6068B
SSDEEP24:ZkbBLmen5LVtAIn6F1GLSnBUE2jAUMpRL1TN0mcmsmSmymE3kQ/x9N0rDFNr3kqA:uIenXitFvBUtdqL1xFdtvPEv/xrI8
TLSHT1FD31EA1E4DB3706176732BC3C8D600A216BBD4151B8EDD88B6095D2C191BF87775A673
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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
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