Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Mar 2, 2024 via pnpm

oauth-sign 0.8.2

OAuth 1 signing. Formerly a vendor lib in mikeal/request, now a standalone module.
Package summary
Share
0
issues
1
license
1
Apache-2.0
Package created
1 Mar 2013
Version published
4 May 2016
Maintainers
3
Total deps
1
Direct deps
0
License
Apache-2.0

Issues

0
This package has no issues

Licenses

Apache License 2.0

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
use-patent-claims
place-warranty
Cannot
hold-liable
use-trademark
Must
include-copyright
include-license
state-changes
include-notice
1 Packages, Including:
oauth-sign@0.8.2
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

0
All Dependencies CSV
β“˜ This is a list of oauth-sign 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities

Visualizations

Frequently Asked Questions

What does oauth-sign do?

OAuth-sign is a standalone module in JavaScript that provides OAuth 1 signing facilities. Previously it functioned as a vendor library in mikeal/request, but it is now available as an independent package. The module's primary function is to facilitate signed HTTP requests via various method signatures including HMAC-SHA1, HMAC-SHA256, RSA-SHA1, and PLAINTEXT. It is used to enhance the security of data transmission between a client and server by ensuring the integrity and authenticity of the data.

How do you use oauth-sign?

To use oauth-sign, you first need to install it in your node.js project. It can be installed using the npm install command as follows:

npm install oauth-sign

After installation, require it in your JavaScript file where you're making the HTTP request:

const oauthSign = require('oauth-sign')

Although there isn't an explicit example provided in the readme, oauth-sign could generally be used in a way similar to below:

const baseString = '...'; // your base string
const secretKey = '...'; // your secret key

// For HMAC-SHA1:
const signatureHmacSha1 = oauthSign.HmacSHA1(baseString, secretKey);
console.log(signatureHmacSha1);

// For HMAC-SHA256:
const signatureHmacSha256 = oauthSign.HmacSHA256(baseString, secretKey);
console.log(signatureHmacSha256);

// For RSA-SHA1:
const signatureRsaSha1 = oauthSign.RsaSHA1(baseString, secretKey);
console.log(signatureRsaSha1);

However, keep in mind that the actual methods may differ and you should always check the source code or official documentation for more concrete usage.

Where are the oauth-sign docs?

OAuth-sign documentation is not directly indicated in the readme content shared above. For the most accurate and detailed documentation, it is recommended to visit the official GitHub repository for oauth-sign at https://github.com/mikeal/oauth-sign. The repo contains the source code which can give insights on how to use the package. In case of more complex use cases or issues, you might find solutions or get recommendations from the community by accessing the "Issues" section of the Github repository.