linkedin-node-new
Advanced tools
Comparing version 0.0.4 to 1.0.0
{ | ||
"name": "linkedin-node-new", | ||
"description": "A NodeJS connector for LinkedIn OAuth2", | ||
"version": "0.0.4", | ||
"author": { | ||
"name": "uh-sem-blee, Co. | typefoo", | ||
"email": "hello@typefoo.com" | ||
"name": "linkedin-node-new ", | ||
"version": "1.0.0", | ||
"description": "", | ||
"main": "index.js", | ||
"scripts": { | ||
"test": "echo \"Error: no test specified\" && exit 1" | ||
}, | ||
"maintainers": [ | ||
{ | ||
"name": "jjosef", | ||
"email": "john@typefoo.com" | ||
} | ||
], | ||
"repository": { | ||
"type": "git", | ||
"url": "https://github.com/typefoo/linkedin-node-new" | ||
"url": "git+https://github.com/npm/deprecate-holder.git" | ||
}, | ||
"devDependencies": { | ||
"prompt": ">= 0.2.11" | ||
}, | ||
"main": "./lib/linkedin", | ||
"engines": { | ||
"node": ">= 0.10.0" | ||
}, | ||
"readmeFilename": "README.md", | ||
"author": "", | ||
"license": "ISC", | ||
"bugs": { | ||
"url": "https://github.com/typefoo/linkedin-node-new/issues" | ||
"url": "https://github.com/npm/deprecate-holder/issues" | ||
}, | ||
"_id": "linkedin-node-new@0.0.2", | ||
"_from": "linkedin-node-new@" | ||
"homepage": "https://github.com/npm/deprecate-holder#readme" | ||
} |
@@ -1,59 +0,5 @@ | ||
# LinkedIn Node | ||
# Deprecated Package | ||
npm install linkedin-node-new | ||
This package is no longer supported and has been deprecated. To avoid malicious use, npm is hanging on to the package name. | ||
You can run the test by cloning this repo and running: | ||
npm install | ||
node test/test | ||
For setting up: | ||
var linkedInObj = require('linkedin-node-new'); | ||
var linkedIn = new linkedInObj({ | ||
id: 'MYCLIENTID', | ||
secret: 'MYCLIENTSECRET', | ||
scope: '', // optional, set the scope of your app | ||
redirect_uri: 'http://localhost:9000/#!/oauth/linkedin' | ||
}); | ||
var url = linkedIn.createURL(); | ||
After you have obtained the 'code' (either via your redirect or elsewhere): | ||
var code = ''; // put the short-time auth code in here. | ||
linkedIn.getAccessToken(code, function(err, access_token) { | ||
console.log(err); | ||
console.log(access_token); | ||
}); | ||
If you have saved your access token in some sort of session or cookie data, you can skip the authorization request: | ||
var linkedIn = new linkedInObj({ | ||
id: 'MYCLIENTID', | ||
secret: 'MYCLIENTSECRET', | ||
redirect_uri: 'http://localhost:9000/#!/oauth/linkedin', | ||
access_token: 'MYACCESSTOKEN' | ||
}); | ||
Once authorized, you can perform typical REST services (https://developer.linkedin.com/documents/authentication for reference): | ||
// GET | ||
linkedIn.get('/v1/people/~:(id,first-name,last-name,headline,positions,picture-url,email-address)', function(err, res) { | ||
if(err) { | ||
return console.log(err); | ||
} | ||
console.log(res); | ||
console.log(res.positions.values[0]); | ||
}); | ||
// POST | ||
// PUT | ||
// DELETE | ||
Built in Ohio. www.typefoo.com | ||
Please contact support@npmjs.com if you have questions about this package. |
Empty package
Supply chain riskPackage does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Manifest confusion
Supply chain riskThis package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
No contributors or author data
MaintenancePackage does not specify a list of contributors or an author in package.json.
Found 1 instance in 1 package
No tests
QualityPackage does not have any tests. This is a strong signal of a poorly maintained or low quality package.
Found 1 instance in 1 package
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
No bug tracker
MaintenancePackage does not have a linked bug tracker in package.json.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
No website
QualityPackage does not have a website.
Found 1 instance in 1 package
0
1
681
2
0
6
4