Result for 13EA0BE29FEB0A401B19EA694665F04DD7DC3303

Query result

Key Value
FileName./usr/share/gems/specifications/apipie-rails-0.3.6.gemspec
FileSize2184
MD51F81C3B075ABF02450E4080F949F08C1
SHA-113EA0BE29FEB0A401B19EA694665F04DD7DC3303
SHA-256BC1DC66112448FE8144D788BCC8FC22CDA7856D9F8C6543D34C66858D66C2FA8
SSDEEP24:ZkbcxaO7dsxt1BkG15BUE2wEx5Tp7vzeDuTNzeRZe7eleFeEzI/iQvzwuNzIZ6oK:uBORMTLBUtwEngyxaiSAgEE/tbt/FTd
TLSHT1EE41415A05B3E0B133B334C34CDA00A22AF3D1366B86D048B51D69085B18DDF368EBB7
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
MD50C8D1624A8F1F12147B6368B89B54156
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
PackageRelease1.fc24
PackageVersion0.3.6
SHA-1CD56C277B5DA389520FA6AB93450F151F6E296C6
SHA-2566332155A3552BA990BDABA0B167C4332CBECA3F2D0573BAB121ACCC79D4C7B05
Key Value
MD52BF1E91DFC79AD1F82EF49B05DFA9727
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
PackageRelease1.fc24
PackageVersion0.3.6
SHA-122C754944B2C5F55F86581EC1566B26903A0BC58
SHA-256BBBD265B2F1B3EA639AE9D9F3A4AE8C2C278CD84886371680EC7106943A7F82A