Gathering detailed insights and metrics for eosjs-keos
Gathering detailed insights and metrics for eosjs-keos
Gathering detailed insights and metrics for eosjs-keos
Gathering detailed insights and metrics for eosjs-keos
JavaScript API for using keos as Signature Provider to replace the JsSignatureProvider.
npm install eosjs-keos
Typescript
Module System
Node Version
NPM Version
70.9
Supply Chain
98.2
Quality
75.2
Maintenance
100
Vulnerability
100
License
JavaScript (99.49%)
Shell (0.51%)
Total Downloads
2,961
Last Day
1
Last Week
9
Last Month
17
Last Year
130
MIT License
3 Stars
18 Commits
2 Watchers
1 Branches
1 Contributors
Updated on Jan 14, 2022
Minified
Minified + Gzipped
Latest Version
1989.6.7
Package Id
eosjs-keos@1989.6.7
Unpacked Size
24.42 kB
Size
7.06 kB
File Count
8
NPM Version
7.0.3
Node Version
15.0.1
Cumulative downloads
Total Downloads
Last Day
0%
1
Compared to previous day
Last Week
80%
9
Compared to previous week
Last Month
-32%
17
Compared to previous month
Last Year
7.4%
130
Compared to previous year
1
JavaScript API for using keos as Signature Provider
to replace the JsSignatureProvider
.
1$ npm install eosjs-keos
The official distribution package can be found at npm.
1const { Api, JsonRpc, RpcError } = require('eosjs'); 2const { KeosSignatureProvider } = require('eosjs-keos/sig'); 3const fetch = require('node-fetch'); // node only; not needed in browsers 4const { TextEncoder, TextDecoder } = require('util'); // node only; native TextEncoder/Decoder
The Signature Provider HOLDS
the wallet password
to unlock the wallet to signing transactions.
The Signature Provider DOES NOT HOLD
any private keys
directly.
1const options = { 2 keosApi: 'http://127.0.0.1:8900', 3 wallet: 'keosjs_test', 4 password: 'PWXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', 5}; 6const signatureProvider = new KeosSignatureProvider(options);
It should be a drop in replacement. After these config, you can use native eosjs APIs smoothly. The Signature Provider
will do the rest under the hood. More details can be found here.
skipUnlock: false
by default. You can enable this option skipUnlock: true
to turn off the auto-unlock feature for extreme security. The Signature Provider can be run WITHOUT
any password
or key
configurations. You have to lock/unlock the wallet all by yourself.
checkBeforeUnlock: false
by default. This means the Signature Provider will try to unlock the wallet whenever needed. It's fast and stable but will case annoying logs in the keosd
console.
Example:
1thread-0 http_plugin.cpp:932 handle_exception ] FC Exception encountered while processing wallet.unlock
Set checkBeforeUnlock: true
will force The Signature Provider to query and determine if the wallet needs to be unlocked, before actually unlock runs. It's a little bit slower but you can get a cleaner keosd console. It might cause issues when the wallet-unlock timeouts after check-action and before sign-action.
1const KEOS = require('eosjs-keos'); 2const keos = new KEOS({ /* options */ });
API available:
1const CHAIN = require('eosjs-keos/chain'); 2const chain = new CHAIN({ /* options */ });
API available:
1$ npm test
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
Found 0/18 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2025-05-05
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