This is the official Cloudant library for Node.js.
The best way to use the Cloudant client is to begin with your own Node.js project, and define this work as your dependency. In other words, put me in your package.json dependencies. The npm tool can do this for you, from the command line:
$ npm install --save cloudant
Notice that your package.json will now reflect this package. Everything is working if you can run this command with no errors:
$ node -e 'require("cloudant"); console.log("Cloudant works");'
Cloudant works
Now it's time to begin doing real work with Cloudant and Node.js.
Initialize your Cloudant connection by supplying your account and password, and supplying a callback function to run when everything is ready.
var Cloudant = require('cloudant')
var me = 'jhs' // Set this to your own account
var password = process.env.cloudant_password
Cloudant({account:me, password:password}, function(err, cloudant) {
console.log('Connected to Cloudant')
cloudant.db.list(function(err, all_dbs) {
console.log('All my databases: %s', all_dbs.join(', '))
})
})
Output:
Connected to Cloudant
All my databases: example_db, jasons_stuff, scores
Upper-case Cloudant is this package you load using require(), while lower-case cloudant represents an authenticated, confirmed connection to your Cloudant service.
If you omit the "password" field, you will get an "anonymous" connection: a client that sends no authentication information (no passwords, no cookies, etc.)
To use the example code as-is, you must first install the dotenv package from npm, then create a .env file with your Cloudant credentials. For example:
npm install dotenv # Install ./node_modules/dotenv
echo "/.env" >> .gitignore # Do not track .env in the revision history
echo "cloudant_username=myaccount" > .env # Replace myaccount with your account name
echo "cloudant_password='secret'" >> .env # Replace secret with your password
Here is simple but complete example of working with data:
require('dotenv').load()
var Cloudant = require('Cloudant')
var me = process.env.cloudant_username
var password = process.env.cloudant_password
Cloudant({account:me, password:password}, function(er, cloudant) {
if (er)
return console.log('Error connecting to Cloudant account %s: %s', me, er.message)
// Clean up the database we created previously.
cloudant.db.destroy('alice', function() {
// Create a new database.
cloudant.db.create('alice', function() {
// specify the database we are going to use
var alice = cloudant.use('alice')
// and insert a document in it
alice.insert({ crazy: true }, 'rabbit', function(err, body, header) {
if (err)
return console.log('[alice.insert] ', err.message)
console.log('you have inserted the rabbit.')
console.log(body)
})
})
})
})
If you run this example, you will see:
you have inserted the rabbit.
{ ok: true,
id: 'rabbit',
rev: '1-6e4cb465d49c0368ac3946506d26335d' }
To use Cloudant, require('cloudant') in your code. That will return the initialization function. Run that function, passing your account name and password, and a callback. (And see the security note about placing your password into your source code.
var Cloudant = require('cloudant')
// Connect to Cloudant.
Cloudant({account:me, password:password}, function(er, cloudant) {
if (er)
return console.log('Error connecting to Cloudant account %s: %s', me, er.message)
console.log('Connected to cloudant')
/*
* The rest of my code goes here.
*/
})
If you would prefer, you can also initialize Cloudant synchronously by omitting the callback.
This can help avoid messy code if you are requiring the Cloudant library in many places in your app. You should note that this method does not verify that your Cloudant credentials are correct - you would have to use the ping for that.
A simple example of initializing sychronously is:
var Cloudant = require('cloudant')({account:me, password:password});
var db = Cloudant.use("animals");
db.get("dog", function(err, data) {
// rest of your code goes here
});
Ping Cloudant. If this succeeds, then you have a good connection to Cloudant, and if you provided authentication credentials, they are valid.
cloudant.ping(function(er, reply) {
if (er)
return console.log('Failed to ping Cloudant')
console.log('Server version = %s', reply.version)
console.log('I am %s and my roles are %j', reply.userCtx.name, reply.userCtx.roles)
})
After initialization, in general, callback functions receive three arguments:
err - the error, if anybody - the http response body from Cloudant, if no error.
json parsed body, binary for non json responsesheader - the http response header from Cloudant, if no errorThe ping() function is the only exception to this rule. It does not return headers since a "ping" is made from multiple requests to gather various bits of information.
By default, when you connect to your cloudant account (i.e. "me.cloudant.com"), you authenticate as the account owner (i.e. "me"). However, you can use Cloudant with any username and password. Just provide an additional "username" option when you initialize Cloudant. This will connect to your account, but using the username as the authenticated user. (And of course, use the appropriate password.)
Cloudant({account:"me", username:"somebody", password:"somebody's secret"}, function(er, cloudant, reply) {
if (er)
throw er
console.log('Connected with username: %s', reply.userCtx.name)
})
If you use Cloudant Local, everything works exactly the same, except you provide a hostname parameter to indicate which server to use:
Cloudant({hostname:"companycloudant.local", username:"somebody", password:"somebody's secret"}, function(er, cloudant, reply) {
if (er)
throw er
console.log('Connected with username: %s', reply.userCtx.name)
})
This feature interfaces with the Cloudant authorization API.
Use the authorization feature to generate new API keys to access your data. An API key is basically a username/password pair for granting others access to your data, without giving them the keys to the castle.
cloudant.generate_api_key(function(er, api) {
if (er)
throw er // You probably want wiser behavior than this.
console.log('API key: %s', api.key)
console.log('Password for this key: %s', api.password)
Output:
API key: isdaingialkyciffestontsk
Password for this key: XQiDHmwnkUu4tknHIjjs2P64
Next, set access roles for this API key:
// Set the security for three users.
var db = "my_database",
security = {
cloudant: {
nobody: []
fred : [ '_reader', '_writer', '_admin', '_replicator' ],
isdaingialkyciffestontsk: [ '_reader', '_writer' ]
}
};
cloudant.set_security( database, security, function(er, result) {
if (er)
throw er
console.log(result);
});
or read the security settings for a database
var db = "my_database",
cloudant.view_security( database, function(er, result) {
if (er)
throw er
console.log(result);
});
Output:
{
"cloudant": {
"nobody": [],
"fred": [
"_reader",
"_writer",
"_admin",
"_replicator"
],
"isdaingialkyciffestontsk": [
"_reader",
"_writer"
]
}
}
See the Cloudant API for full details](https://docs.cloudant.com/api.html#authorization)
To use an API key, initialize a new Cloudant connection, and provide an additional "key" option when you initialize Cloudant. This will connect to your account, but using the "key" as the authenticated user. (And of course, use the appropriate password associated with the API key.)
Cloudant({account:"me", key:api.key, password:api.password}, function(er, cloudant, reply) {
if (er)
throw er
console.log('Connected with API key %s', reply.userCtx.name)
})
If you need to access your Cloudant database from a web application that is served from a domain other than your Cloudant account, you will need to enable CORS (Cross-origin resource sharing).
e.g. enable CORS from any domain:
cloudant.cors({ enable_cors: true, allow_credentials: true, origins: ["*"]}, function(err, data) {
console.log(err, data);
};
or enable access from a list of specified domains:
cloudant.cors({ enable_cors: true, allow_credentials: true, origins: [ "https://mydomain.com","https://mysubdomain.mydomain.com"]}, function(err, data) {
console.log(err, data);
};
or disable CORS access
cloudant.cors({ enable_cors: false }, function(err, data) {
console.log(err, data);
};
See https://docs.cloudant.com/api.html#cors for further details.
Once Cloudant is initialized without errors, your callback has a cloudant object representing your connection to the server. To work with databases, use these database functions. (To work with data inside the databases, see below.)
Create a Cloudant database with the given name.
cloudant.db.create('alice', function(err, body) {
if (!err)
console.log('database alice created!')
})
Get information about name.
cloudant.db.get('alice', function(err, body) {
if (!err)
console.log(body)
})
Destroy database named name.
cloudant.db.destroy('alice', function(err) {
if (!err)
console.log('Destroyed database alice')
})
List all the databases in Cloudant server.
cloudant.db.list(function(err, body) {
// body is an array
body.forEach(function(db) {
console.log(db)
})
})
Replicates source to target with options opts. target
must exist, add create_target:true to opts to create it prior to
replication.
cloudant.db.replicate('alice', 'http://admin:password@otherhost.com:5984/alice',
{ create_target:true }, function(err, body) {
if (!err)
console.log(body)
})
Asks for the changes feed of name, params contains additions
to the query string.
cloudant.db.changes('alice', function(err, body) {
if (!err)
console.log(body)
})
Use Follow to create a solid changes feed. Please consult the Follow documentation for more information as this is a very complete api on it's own.
var feed = db.follow({since: "now"})
feed.on('change', function (change) {
console.log("change: ", change);
})
feed.follow();
process.nextTick(function () {
db.insert({"bar": "baz"}, "bar");
});
Create a new database object for operating within the scope of a specific database.
var alice = cloudant.db.use('alice')
alice.insert({ crazy: true }, 'rabbit', function(err, body) {
// do something
})
Make a custom request to Cloudant, the available opts are:
opts.db – the database nameopts.method – the http method, defaults to getopts.path – the full path of the request, overrides opts.doc and
opts.attopts.doc – the document nameopts.att – the attachment nameopts.qs – query string parameters, appended after any existing opts.path, opts.doc, or opts.attopts.content_type – the content type of the request, default to jsonopts.headers – additional http headers, overrides existing onesopts.body – the document or attachment bodyopts.encoding – the encoding for attachmentsopts.multipart – array of objects for multipart requestAn object containing the Cloudant configurations, possible keys are:
url - the Cloudant urldb - the database nameListen to db updates, the available params are:
params.feed – Type of feed. Can be one oflongpoll: Closes the connection after the first event.continuous: Send a line of JSON per event. Keeps the socket open until timeout.eventsource: Like, continuous, but sends the events in EventSource format.params.timeout – Number of seconds until CouchDB closes the connection. Default is 60.params.heartbeat – Whether CouchDB will send a newline character (\n) on timeout. Default is true.Uses follow to create a solid
_db_updates feed.
please consult follow documentation for more information as this is a very complete api on it's own
var feed = Cloudant.followUpdates({since: "now"})
feed.on('change', function (change) {
console.log("change: ", change)
})
feed.follow()
process.nextTick(function () {
cloudant.db.create('alice')
})
Once you run cloudant.db.use('db_name'), use the returned object to work with documents in the database.
Insert doc in the database. The first parameter (an object) is the document body. The second parameter is the document ID.
var alice = cloudant.use('alice')
alice.insert({ crazy: true }, 'rabbit', function(err, body) {
if (!err)
console.log(body)
})
Get doc_id from the database with optional query string additions params.
alice.get('rabbit', { revs_info: true }, function(err, body) {
if (!err)
console.log(body);
});
Remove revision rev of doc_id from the Cloudant database.
alice.destroy('rabbit', '3-66c01cdf99e84c83a9b3fe65b88db8c0', function(err, body) {
if (!err)
console.log(body)
})
Same as get but lightweight version that returns headers only.
alice.head('rabbit', function(err, _body, headers) {
// In fact, _body is empty.
if (!err)
console.log(headers)
})
copy the contents (and attachments) of a document
to a new document, or overwrite an existing target document
alice.copy('rabbit', 'rabbit2', { overwrite: true }, function(err, _, headers) {
if (!err)
console.log(headers)
})
Bulk operations(update/delete/insert) on the database, refer to the Documentation.
List all the docs in the database with optional query string additions params.
alice.list(function(err, body) {
if (!err) {
body.rows.forEach(function(doc) {
console.log(doc)
})
}
})
Bulk fetch of the database documents, doc_ids are specified as per
CouchDB doc.
Additional query string params can be specified, include_docs is always set
to true.
Bulk fetch of the revisions of the database documents, doc_ids are specified as per
CouchDB doc.
Additional query string params can be specified, this is the same method as fetch but
include_docs is not automatically set to true.
The multipart functions are for efficiently working with documents and attachments, by using a special feature of HTTP: the "multipart/related" content type. Requests that use multipart/related separate the content into different pieces, with each piece encoded in a different way. In practice, this means sending a JSON document plus binary attachments to Cloudant in a single, efficient, request.
Insert a doc together with attachments and optional params. If params is a string, its assumed as the intended document name. if params is an object, its passed as query string parameters and docName is checked for defining the document name. Refer to the CouchDB multipart documentation for more details.
attachments must be an array of objects with name, data and content_type properties. For example:
var fs = require('fs')
fs.readFile('rabbit.png', function(err, data) {
if (!err) {
var img = {name:'rabbit.png', content_type:'image/png', data:data}
var attachments = [img] // An array with one attachment, the rabbit image
alice.multipart.insert({ ears: 2 }, attachments, 'rabbit', function(err, body) {
if (!err)
console.log(body)
})
}
})
Get doc_id together with its attachments via multipart/related request with optional query string additions
params. Refer to the doc for more details. The multipart response body is a Buffer.
alice.multipart.get('rabbit', function(err, buffer) {
if (!err)
console.log(buffer.toString())
})
Inserts an attachment attname to doc_id. In most cases params.rev is required. Refer to the doc for more details.
var fs = require('fs')
fs.readFile('rabbit.png', function(err, data) {
if (!err) {
alice.attachment.insert('rabbit', 'rabbit.png', data, 'image/png',
{ rev: '12-150985a725ec88be471921a54ce91452' }, function(err, body) {
if (!err)
console.log(body)
})
}
})
If you use null as the data parameter, then this function returns a writable stream, to which you can pipe the attachment data.
var fs = require('fs')
var img_stream = fs.createReadStream('rabbit.png')
var attachment = alice.attachment.insert('new', 'rabbit.png', null, 'image/png')
img_stream.pipe(attachment)
Get doc_id's attachment attname with optional query string additions params.
var fs = require('fs')
alice.attachment.get('rabbit', 'rabbit.png', function(err, body) {
if (!err)
fs.writeFile('rabbit.png', body)
})
This function also returns a readable stream, which you may pipe to a writable stream.
Or using pipe:
var fs = require('fs')
var img_stream = fs.createWriteStream('rabbit.png')
var attachment = alice.attachment.get('rabbit', 'rabbit.png')
attachment.pipe(img_stream)
Destroy attachment attname of docname's revision rev.
var rev = '1-4701d73a08ce5c2f2983bf7c9ffd3320'
alice.attachment.destroy('rabbit', 'rabbit.png', {'rev':rev}, function(err, body) {
if (!err)
console.log(body)
})
These functions are for working with views and design documents, including querying the database using map-reduce views, Cloudant Search, and Cloudant Query.
Call a view of the specified design with optional query string additions
params. If you're looking to filter the view results by key(s) pass an array of keys, e.g
{ keys: ['key1', 'key2', 'key_n'] }, as params.
alice.view('characters', 'crazy_ones', function(err, body) {
if (!err)
body.rows.forEach(function(doc) {
console.log(doc.value)
})
})
Call a view of the specified design with optional query string additions params. See the Cloudant Search section below for more details.
alice.search('characters', 'crazy_ones', { q: 'cat' }, function(err, doc) {
if (!err) {
console.log(doc);
}
});
This feature interfaces with Cloudant's query functionality. See the Cloudant Query documentation for details.
As with Nano, when working with a database (as opposed to the root server), run the .use() method.
var db = cloudant.use('my_db')
To see all the indexes in a database, call the database .index() method with a callback function.
db.index(function(er, result) {
if (er)
throw er
console.log('The database has %d indexes', result.indexes.length)
for (var i = 0; i < result.indexes.length; i++)
console.log(' %s (%s): %j', result.indexes[i].name, result.indexes[i].type, result.indexes[i].def)
})
Example output:
The database has 3 indexes
_all_docs (special): {"fields":[{"_id":"asc"}]}
first-name (json): {"fields":[{"name":"asc"}]}
last-name (json): {"fields":[{"name":"asc"}]}
To create an index, use the same .index() method but with an extra initial argument: the index definition. For example, to make an index on middle names in the data set:
var middle_name = {name:'middle-name', type:'json', index:{fields:['middle']}}
db.index(middle_name, function(er, response) {
if (er)
throw er
console.log('Index creation result: %s', response.result)
})
Output:
Index creation result: created
To query using the index, use the .find() method.
db.find({selector:{name:'Alice'}}, function(er, result) {
if (er)
throw er
console.log('Found %d documents with name Alice')
for (var i = 0; i < result.docs.length; i++)
console.log(' Doc id: %s', result.docs[i]._id)
})
This feature interfaces with Cloudant's search functionality. See the Cloudant Search documentation for details.
First, when working with a database (as opposed to the root server), run the .use() method.
var db = cloudant.use('my_db')
To create a Cloudant Search index, create a design document the normal way you would with Nano, the database .insert() method.
To see all the indexes in a database, call the database .index() method with a callback function.
, {_id: '_design/library', indexes:{books:{analyzer:{name:'standard'}, index:index}}}
// Note, you can make a normal JavaScript function. It is not necessary
// for you to convert it to a string as with other languages and tools.
var book_indexer = function(doc) {
// Index the title and author of books.
if (doc.type == 'book') {
index('title', doc.title)
index('author', doc.author)
}
}
var ddoc = { _id: '_design/library'
, indexes:
{ books:
{ analyzer: {name: 'standard'}
, index : book_indexer
}
}
}
db.insert(ddoc, function (er, result) {
if (er)
throw er
else
console.log('Created design document with books index')
})
To query this index, use the database .search() method. The first argument is the design document name, followed by the index name, and finally an object with your search parameters.
db.search('library', 'books', {q:'author:dickens'}, function(er, result) {
if (er)
throw er
console.log('Showing %d out of a total %d books by Dickens', result.rows.length, result.total_rows)
for (var i = 0; i < result.rows.length; i++)
console.log('Document id: %s', result.rows.id)
})
Cloudant supports making requests using Cloudant's cookie authentication functionality. there's a step-by-step guide here, but essentially you just:
var Cloudant = require('Cloudant')
var username = 'user'
var userpass = 'pass'
// A global variable to store the cookies. This can be on the filesystem or some other cache, too.
var cookies = {}
Cloudant({account:username, password:userpass}, function(err, cloudant) {
if (err)
return console.log('Failed to connect to Cloudant: ' + err.message)
// In this example, we authenticate using the same username/userpass as above.
// However, you can use a different combination to authenticate as other users
// in your database. This can be useful for using a less-privileged account.
cloudant.auth(username, userpass, function(err, body, headers) {
if (err)
return console.log('Error authenticating: ' + err.message)
console.log('Got cookie for %s: %s', username, headers['set-cookie'])
// Store the authentication cookie for later.
cookies[username] = headers['set-cookie']
})
})
To reuse a cookie:
// Make a new connection with the cookie.
Cloudant({account:username, cookie:cookies[username]}, function(err, other_cloudant) {
if (err)
return console.log('Failed to connect to Cloudant: ' + err.message)
console.log('Connected to Cloudant using a cookie!')
var alice = other_cloudant.use('alice')
alice.insert({_id:"my_doc"}, function (err, body, headers) {
if (err)
return console.log('Failed to insert into alice database: ' + err.message)
// Change the cookie if Cloudant tells us to.
if (headers && headers['set-cookie'])
cookies[username] = headers['set-cookie']
})
})
Getting current session:
var Cloudant = require('Cloudant')({url: 'http://localhost:5984', cookie: 'AuthSession=' + auth});
Cloudant.session(function(err, session) {
if (err) {
return console.log('oh noes!')
}
console.log('user is %s and has these roles: %j',
session.userCtx.name, session.userCtx.roles);
});
Besides the account and password options, you can add an optionsl requestDefaults value, which will initialize Request (the underlying HTTP library) as you need it.
var Cloudant = require('Cloudant')
// Use an HTTP proxy to connect to Cloudant.
var options =
{ "account" : "my_account"
, "password" : "secret"
, "requestDefaults": { "proxy": "http://localhost:8080" }
}
Cloudant(options, function(err, cloudant) {
// Now using the HTTP proxy...
})
Please check request for more information on the defaults. They support features like cookie jar, proxies, ssl, etc.
A very important configuration parameter if you have a high traffic website and are using Cloudant is setting up the pool.size. By default, the node.js https global agent (client) has a certain size of active connections that can run simultaneously, while others are kept in a queue. Pooling can be disabled by setting the agent property in requestDefaults to false, or adjust the global pool size using:
var https = require('https')
https.globalAgent.maxSockets = 20
You can also increase the size in your calling context using requestDefaults if this is problematic. refer to the request documentation and examples for further clarification.
Here is an example of explicitly using the keep alive agent (installed using npm install agentkeepalive), especially useful to limit your open sockets when doing high-volume access to Cloudant:
var agentkeepalive = require('agentkeepalive')
var myagent = new agentkeepalive({
maxSockets: 50
, maxKeepAliveRequests: 0
, maxKeepAliveTime: 30000
})
var Cloudant = require('cloudant')
Cloudant({account:"me", password:"secret", requestDefaults:{agent:myagent}}, function(err, cloudant) {
// Using Cloudant with myagent...
})
Cloudant is minimalistic but you can add your own features with cloudant.request(opts, callback)
For example, to create a function to retrieve a specific revision of the rabbit document:
function getrabbitrev(rev, callback) {
cloudant.request({ db: 'alice',
doc: 'rabbit',
method: 'get',
params: { rev: rev }
}, callback)
}
getrabbitrev('4-2e6cdc4c7e26b745c2881a24e0eeece2', function(err, body) {
if (!err)
console.log(body)
})
You can pipe in Cloudant like in any other stream. for example if our rabbit document has an attachment with name picture.png (with a picture of our white rabbit, of course!) you can pipe it to a writable stream
See the Attachment Functions section for examples of piping to and from attachments.
to run (and configure) the test suite simply:
cd Cloudant
npm install
npm test
after adding a new test you can run it individually (with verbose output) using:
Cloudant_env=testing node tests/doc/list.js list_doc_params
where list_doc_params is the test name.
To join the effort developing this project, start from our GitHub page: https://github.com/cloudant/nodejs-cloudant
First clone this project from GitHub, and then install its dependencies using npm.
$ git clone https://github.com/cloudant/nodejs-cloudant
$ npm install
We use npm to handle running the test suite. To run the comprehensive test suite, just run npm test. However, to run only the Cloudant-specific bits, we have a custom test-cloudant script.
$ npm run test-cloudant
> cloudant@5.10.1 test-cloudant /Users/jhs/src/cloudant/nodejs-cloudant
> env NOCK=on sh tests/cloudant/run-tests.sh
Test against mocked local database
/tests/cloudant/auth.js
✔ 5/5 cloudant:generate_api_key took 196ms
✔ 3/3 cloudant:set_permissions took 7ms
✔ 8/8 summary took 224ms
<...cut a bunch of test output...>
This runs against a local "mock" web server, called Nock. However the test suite can also run against a live Cloudant service. I have registered "nodejs.cloudant.com" for this purpose. To use it, run the test-cloudant-live script.
$ npm run test-cloudant-live
> cloudant@5.10.1 test-cloudant-live /Users/jhs/src/cloudant/nodejs-cloudant
> sh tests/cloudant/run-tests.sh
Test against mocked local database
/tests/cloudant/auth.js
✔ 5/5 cloudant:generate_api_key took 192ms
✔ 3/3 cloudant:set_permissions took 7ms
✔ 8/8 summary took 221ms
<...cut a bunch of test output...>
Unfortunately you need to know the password.
$ npm run test-cloudant-live
> cloudant@5.10.1 test-cloudant-live /Users/jhs/src/cloudant/nodejs-cloudant
> sh tests/cloudant/run-tests.sh
Test against remote Cloudant database
No password configured for remote Cloudant database. Please run:
npm config set cloudant_password "<your-password>"
npm ERR! cloudant@5.10.1 test-cloudant-live: `sh tests/cloudant/run-tests.sh`
<...cut npm error messages...>
Get the password from Jason somehow, and set it as an npm variable.
# Note the leading space to keep this command out of the Bash history.
$ HISTCONTROL="$HISTCONTROL:ignorespace"
$ npm config set cloudant_password "ask jason for the password" # <- Not the real password
$ npm run test-cloudant-live
<...cut successful test suite run...>
If you work on this project plus another one, your best bet is to clone from GitHub and then link this project to your other one. With linking, your other project depends on this one; but instead of a proper install, npm basically symlinks this project into the right place.
Go to this project and "link" it into the global namespace (sort of an "export").
$ cd cloudant
$ npm link
/Users/jhs/.nvm/v0.10.25/lib/node_modules/cloudant -> /Users/jhs/src/cloudant/nodejs-cloudant
Go to your project and "link" it into there (sort of an "import").
$ cd ../my-project
$ npm link cloudant
/Users/jhs/src/my-project/node_modules/cloudant -> /Users/jhs/.nvm/v0.10.25/lib/node_modules/cloudant -> /Users/jhs/src/cloudant/nodejs-cloudant
Now your project has the dependency in place, however you can work on both of them in tandem.
Copyright 2014 Cloudant, an IBM company.
Licensed under the apache license, version 2.0 (the "license"); you may not use this file except in compliance with the license. you may obtain a copy of the license at
http://www.apache.org/licenses/LICENSE-2.0.html
Unless required by applicable law or agreed to in writing, software distributed under the license is distributed on an "as is" basis, without warranties or conditions of any kind, either express or implied. See the license for the specific language governing permissions and limitations under the license.
FAQs
Cloudant Node.js client
The npm package cloudant receives a total of 3,564 weekly downloads. As such, cloudant popularity was classified as popular.
We found that cloudant demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.