Result for 1B8BCDE62F8834AEBE4733397979F9DF4C4CCD95

Query result

Key Value
FileName./usr/share/gems/gems/apipie-rails-0.5.5/lib/apipie/apipie_module.rb
FileSize1836
MD5D413793A15B5F3D59FDE1265143955A3
SHA-11B8BCDE62F8834AEBE4733397979F9DF4C4CCD95
SHA-256C061DFE455A7DF099C6008786635FBFF30498795AB3136A7E238931531225B9D
SSDEEP48:ovMnhy4Grry0fN66Ic7U6xQa6A/301oUM2oaMd/DXFCwooFA5wT:o0QbhYc7fxQFABDT7FCwFF0wT
TLSHT177319BDA154AE8F7A4579B4F90833807AF7A879A318D2924BE7F105A5F0016D6343F28
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