Result for 0201B18820E5116F73C26EC40FCB2A363CF9D73D

Query result

Key Value
FileName./usr/share/gems/gems/apipie-rails-0.5.5/lib/apipie-rails.rb
FileSize666
MD5907E3A1BBC17178BED1BFD65BA640581
SHA-10201B18820E5116F73C26EC40FCB2A363CF9D73D
SHA-256061F6452B54C95995305217FB2CB7F088DD5A3152074BFDCB30614A55C32E061
SSDEEP12:7HLC+TbbtOh2FHL2XxaN+nPYYs8CFRRcpQxB0ARx:XC+TkEZkW8CFnBn
TLSHT1F60119C87BD5A421258A02D4689F6008FA77C795E844BB02F8D4D0FDF8C89E26BA5B30
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