Gathering detailed insights and metrics for paseto
Gathering detailed insights and metrics for paseto
Installations
npm install pasetoScore
98.6
Supply Chain
100
Quality
76
Maintenance
100
Vulnerability
100
License
Developer
panva
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
>=16.0.0
Typescript Support
Yes
Node Version
18.16.0
NPM Version
9.5.1
Statistics
456 Stars
154 Commits
27 Forks
7 Watching
6 Branches
5 Contributors
Updated on 22 Nov 2024
Languages
JavaScript (95.95%)
TypeScript (4.05%)
Total Downloads
Cumulative downloads
Total Downloads
4,995,210
Last day
-14.9%
5,659
Compared to previous day
Last week
5.6%
35,354
Compared to previous week
Last month
31.7%
132,331
Compared to previous month
Last year
-11.7%
1,565,139
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
6
Versions
paseto
PASETO: Platform-Agnostic SEcurity TOkens for Node.js with no dependencies.
Implemented Protocol Versions
| v1 | v2 | v3 | v4 | |
|---|---|---|---|---|
| local | ✅ | ❌ | ✅ | ❌ |
| public | ✅ | ✅ | ✅ | ✅ |
Support
If you or your business use paseto, please consider becoming a sponsor so I can continue maintaining it and adding new features carefree.
Documentation
Usage
Installing paseto
1npm install paseto
Usage
1const paseto = require('paseto') 2 3// Generic (all versions) APIs 4const { decode } = paseto 5 6// PASETO Protocol Version v1 specific API 7const { V1 } = paseto // { sign, verify, encrypt, decrypt, generateKey } 8 9// PASETO Protocol Version v2 specific API 10const { V2 } = paseto // { sign, verify, generateKey } 11 12// PASETO Protocol Version v3 specific API 13const { V3 } = paseto // { sign, verify, encrypt, decrypt, generateKey } 14 15// PASETO Protocol Version v4 specific API 16const { V4 } = paseto // { sign, verify, generateKey } 17 18// errors utilized by paseto 19const { errors } = paseto
Producing tokens
1const { V4: { sign } } = paseto 2 3(async () => { 4 { 5 const token = await sign({ sub: 'johndoe' }, privateKey) 6 // v4.public.eyJzdWIiOiJqb2huZG9lIiwiaWF0IjoiMjAyMS0wOC0wM1QwNTozOTozNy42NzNaIn3AW3ri7P5HpdakJmZvhqssz7Wtzi2Rb3JafwKplLoCWuMkITYOo5KNNR5NMaeAR6ePZ3xWUcbO0R11YLb02awO 7 } 8})()
Consuming tokens
1const { V4: { verify } } = paseto 2 3(async () => { 4 { 5 const payload = await verify(token, publicKey) 6 // { sub: 'johndoe', iat: '2019-07-01T15:22:47.982Z' } 7 } 8})()
FAQ
Supported Library Versions
| Version | Security Fixes 🔑 | Other Bug Fixes 🐞 | New Features ⭐ | Node.js version supported |
|---|---|---|---|---|
| 3.x.x | ✅ | ✅ | ✅ | >= 16.0.0 |
| 2.x.x | ✅ | ❌ | ❌ | ^12.19.0 || >=14.15.0 |
| 1.x.x | ✅ | ❌ | ❌ | >= 12.0.0 |
Semver?
Yes. Everything that's either exported in the TypeScript definitions file or documented is subject to Semantic Versioning 2.0.0. The rest is to be considered private API and is subject to change between any versions.
How do I use it outside of Node.js
It is only built for Node.js environment versions >=16.0.0
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE.md:0
- Info: FSF or OSI recognized license: MIT License: LICENSE.md:0
Reason
3 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
Reason
SAST tool is not run on all commits -- score normalized to 6
Details
- Warn: 6 commits out of 9 are checked with a SAST tool
Reason
branch protection is not maximal on development and all release branches
Details
- Info: 'allow deletion' disabled on branch 'main'
- Info: 'force pushes' disabled on branch 'main'
- Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
- Warn: could not determine whether codeowners review is allowed
- Warn: no status checks found to merge onto branch 'main'
- Warn: PRs are not required to make changes on branch 'main'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings
Reason
3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:35: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:47: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:51: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:52: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/paseto/test.yml/main?enable=pin
- Info: 0 out of 11 GitHub-owned GitHubAction dependencies pinned
- Info: 1 out of 1 third-party GitHubAction dependencies pinned
Reason
Found 2/23 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/release.yml:32
- Warn: no topLevel permission defined: .github/workflows/lock.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Score
4.1
/10
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More