Sha256: 2a856445704d4a7106777da8924b7012b06dda4675f827c023534d9499fcd31b
Contents?: true
Size: 1.56 KB
Versions: 4
Compression:
Stored size: 1.56 KB
Contents
{
"author": {
"name": "Dominic Tarr",
"email": "dominic.tarr@gmail.com",
"url": "dominictarr.com"
},
"name": "crypto-browserify",
"description": "partial implementation of crypto for the browser",
"version": "0.2.1",
"homepage": "https://github.com/dominictarr/crypto-browserify",
"repository": {
"type": "git",
"url": "git://github.com/dominictarr/crypto-browserify.git"
},
"scripts": {
"test": "node test/simple.js"
},
"engines": {
"node": "*"
},
"dependencies": {},
"devDependencies": {
"tape": "~0.1.5"
},
"optionalDependencies": {},
"readme": "# crypto-browserify\n\nA (partial) port of `crypto` to the browser.\n\n\n[](https://travis-ci.org/dominictarr/crypto-browserify)\n\n[](http://ci.testling.com/dominictarr/crypto-browserify)\n\n\nBasically, I found some crypto implemented in JS lieing on the internet somewhere\nand wrapped it in the part of the `crypto` api that I am currently using.\n\nIn a way that will be compatible with [browserify](https://github.com/substack/node-browserify/).\n\nI will extend this if I need more features, or if anyone else wants to extend this,\nI will add you as a maintainer.\n\nProvided that you agree that it should replicate the [node.js/crypto](http://nodejs.org/api/crypto.html) api exactly, of course.\n\n",
"readmeFilename": "readme.markdown",
"_id": "crypto-browserify@0.2.1",
"_from": "crypto-browserify@~0"
}
Version data entries
4 entries across 2 versions & 1 rubygems