Key | Value |
---|---|
FileName | ./usr/lib/node_modules/pg/node_modules/generic-pool |
FileSize | 34 |
MD5 | 38A064314F8D104F15DAB23AAD41A882 |
SHA-1 | 298150D3D87C37F478A1EE1172BC943F159B4833 |
SHA-256 | 194214B899D6FBD3B1C433ECC2B5A851B88B61340C435FE451DB4306B8CD9849 |
SSDEEP | 3:A1lXHgS:AnR |
TLSH | |
hashlookup:parent-total | 21 |
hashlookup:trust | 100 |
The searched file hash is included in 21 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | F332820D498A18ED2CB5D703842860AD |
PackageArch | x86_64 |
PackageDescription | PostgreSQL client for Node.js with pure JavaScript client and native libpq bindings that share the same API. Supported PostgreSQL features include: - parameterized queries - named statements with query plan caching - asynchronous notifications with LISTEN/NOTIFY - bulk import & export with COPY TO/COPY FROM - extensible js<->postgresql data-type coercion |
PackageMaintainer | Fedora Project |
PackageName | nodejs-pg |
PackageRelease | 2.el6 |
PackageVersion | 0.12.3 |
SHA-1 | 0725106EE5D69A79008D180DF01158F8384EB34E |
SHA-256 | 3770C5C7BC4870E67A0A1A42E2D419E3835796BA523CCA121B64EC0969A44BA6 |
Key | Value |
---|---|
MD5 | 68D1C437CC8858131873BA0E4352EB52 |
PackageArch | noarch |
PackageDescription | As of carto 0.2.0, the Carto module expects all data sources and resources to be localized - remote references like URLs and providers are not downloaded when maps are rendered. Millstone now contains this logic - it provides two functions, resolve and flush. Resolve takes an MML file and returns a localized version, and flush can be used to clear the cache of a specific resource. |
PackageMaintainer | Fedora Project |
PackageName | nodejs-millstone |
PackageRelease | 2.fc24 |
PackageVersion | 0.6.17 |
SHA-1 | 09E54BA0970A1F3954028CBB06526E33A52471E2 |
SHA-256 | 5DB39D5E71C004C8C6CBE95A6C2207D234918AFA497AEE70FD49E5FEE381627C |
Key | Value |
---|---|
MD5 | 4559F7A1C30241B4BB4D920355D0CDAB |
PackageArch | noarch |
PackageDescription | If you want to use node-mapnik in an app with concurrency, you'll want to use a map pool. Concurrently using a single map instance can crash your app, and several map instances will give you a significant speedup. mapnik-pool manages a generic-pool of mapnik.Map instances so you don't have to. |
PackageMaintainer | Fedora Project |
PackageName | nodejs-mapnik-pool |
PackageRelease | 9.fc32 |
PackageVersion | 0.1.3 |
SHA-1 | 18CDB5A038AEF9E9D26F8FC39F08382BC30D1697 |
SHA-256 | 31934080C8D0169826FA49069DF4C4F7F92B66114946DB5BD5030451B502CC8D |
Key | Value |
---|---|
MD5 | D08A54874BA09039BE9FFAB67D002C23 |
PackageArch | noarch |
PackageDescription | Renderer backend for tilelive.js that uses node-mapnik to render tiles and grids from a Mapnik XML file. tilelive-mapnik implements the Tilesource API. |
PackageMaintainer | Fedora Project |
PackageName | nodejs-tilelive-mapnik |
PackageRelease | 2.fc24 |
PackageVersion | 0.6.18 |
SHA-1 | 1CC1DBF3DC81EBA7CBFCFABC6261DC9A04EC5B88 |
SHA-256 | 28D1DE0D0A5020D9CE8170228DCD98524734EFDBAC52151029C3CFB2D0A6C79D |
Key | Value |
---|---|
MD5 | 4102766B774CE9D52A31D617C304899F |
PackageArch | i686 |
PackageDescription | PostgreSQL client for Node.js with pure JavaScript client and native libpq bindings that share the same API. Supported PostgreSQL features include: - parameterized queries - named statements with query plan caching - asynchronous notifications with LISTEN/NOTIFY - bulk import & export with COPY TO/COPY FROM - extensible js<->postgresql data-type coercion |
PackageMaintainer | Fedora Project |
PackageName | nodejs-pg |
PackageRelease | 2.el6 |
PackageVersion | 0.12.3 |
SHA-1 | 43AC2C20E504CB15A420AB2FF5EAAE3A8896CCE3 |
SHA-256 | F92176A4C34963997B1DD71E7442AE5177B168178B8CDBB63D89C0B51672CB32 |
Key | Value |
---|---|
MD5 | 912D4B18567CA4DB3DE37173613534A9 |
PackageArch | noarch |
PackageDescription | As of carto 0.2.0, the Carto module expects all data sources and resources to be localized - remote references like URLs and providers are not downloaded when maps are rendered. Millstone now contains this logic - it provides two functions, resolve and flush. Resolve takes an MML file and returns a localized version, and flush can be used to clear the cache of a specific resource. |
PackageMaintainer | Fedora Project |
PackageName | nodejs-millstone |
PackageRelease | 3.fc19 |
PackageVersion | 0.5.15 |
SHA-1 | 5541D0A8C9E51E2BB103C77B978761E93C2BBEA2 |
SHA-256 | EE4B41E5F9C442D808B70191C39AB826BC063F926BA9DF57A58CE3577C0584F9 |
Key | Value |
---|---|
MD5 | 901DA4CAED1060F2562874738ADCA48F |
PackageArch | noarch |
PackageDescription | A network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP or TCP and sends aggregates to one or more pluggable backend services (e.g., Graphite). |
PackageMaintainer | Fedora Project |
PackageName | statsd |
PackageRelease | 1.fc33 |
PackageVersion | 0.8.6 |
SHA-1 | 67FDE8A4C5F05068C2EB297CECE717953F66C889 |
SHA-256 | 7D500F64E8D6F299D75B8DCD5DFFC030B2DE8159A672317D778AFAE320CAC78D |
Key | Value |
---|---|
MD5 | D6375E62BA5B1BDF0EABF8F021336920 |
PackageArch | noarch |
PackageDescription | As of carto 0.2.0, the Carto module expects all data sources and resources to be localized - remote references like URLs and providers are not downloaded when maps are rendered. Millstone now contains this logic - it provides two functions, resolve and flush. Resolve takes an MML file and returns a localized version, and flush can be used to clear the cache of a specific resource. |
PackageMaintainer | Fedora Project |
PackageName | nodejs-millstone |
PackageRelease | 14.fc32 |
PackageVersion | 0.6.17 |
SHA-1 | 6E6F558A9E488404D8A967635EF6BB729EEF5261 |
SHA-256 | 9B0FE7F2D6E54FC923488C0D8099BCAD41C5925999DE3091472F142282B4F898 |
Key | Value |
---|---|
MD5 | CE47BBB3AA31262F28665F2C78178C3A |
PackageArch | noarch |
PackageDescription | If you want to use node-mapnik in an app with concurrency, you'll want to use a map pool. Concurrently using a single map instance can crash your app, and several map instances will give you a significant speedup. mapnik-pool manages a generic-pool of mapnik.Map instances so you don't have to. |
PackageMaintainer | Fedora Project |
PackageName | nodejs-mapnik-pool |
PackageRelease | 2.fc24 |
PackageVersion | 0.1.3 |
SHA-1 | 79DCAB98FA85B1E783C838C9F4D5614DF363DEDC |
SHA-256 | 5DE7B5B85C8C519DE1752A5A8074BC29F880B2AF8C0412BFEFE0084D7F67EC94 |
Key | Value |
---|---|
MD5 | EC5CA77993D138B9126E6ABC985C6D75 |
PackageArch | noarch |
PackageDescription | If you want to use node-mapnik in an app with concurrency, you'll want to use a map pool. Concurrently using a single map instance can crash your app, and several map instances will give you a significant speedup. mapnik-pool manages a generic-pool of mapnik.Map instances so you don't have to. |
PackageMaintainer | Fedora Project |
PackageName | nodejs-mapnik-pool |
PackageRelease | 2.fc24 |
PackageVersion | 0.1.3 |
SHA-1 | 7B71EB96795909FBBE4A28914B11AFEE346D2BAE |
SHA-256 | 9E1EFB9BCA1DEB710FCE7FC4C63D7C2AAA62B893EDE6C3563081AC6172517139 |