Gathering detailed insights and metrics for typed-chrome-webstore-api
Gathering detailed insights and metrics for typed-chrome-webstore-api
Gathering detailed insights and metrics for typed-chrome-webstore-api
Gathering detailed insights and metrics for typed-chrome-webstore-api
Typed Chrome Webstore API to upload/publish extensions
npm install typed-chrome-webstore-api
Typescript
Module System
Min. Node Version
Node Version
NPM Version
TypeScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
2 Stars
36 Commits
1 Watchers
2 Branches
1 Contributors
Updated on Mar 20, 2025
Latest Version
0.4.16
Package Id
typed-chrome-webstore-api@0.4.16
Unpacked Size
29.30 kB
Size
7.70 kB
File Count
17
NPM Version
10.1.0
Node Version
20.9.0
Published on
Nov 12, 2023
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
1
4
Typed Chrome Webstore API to upload/publish extensions and downloading crx file
npm install typed-chrome-webstore-api
See https://developer.chrome.com/webstore/using_webstore_api to understand methods meaning and know how to get
client_id
, client_secret
and refresh_token
strings needed for authentication.
To work with Webstore API you need to get token first:
1const fetchToken = require('typed-chrome-webstore-api').fetchToken; 2const token = fetchToken('clientId', 'clientSecret', 'refreshToken');
Then create WebstoreApi
instance initialized with token:
1const WebstoreApi = require('typed-chrome-webstore-api').WebstoreApi; 2const api = new WebstoreApi(token);
1// Any Readable stream or Buffer 2const zip = fs.createReadStream('./mypackage.zip'); 3// Result format is defined as IWebstoreResource in d.ts file 4const result = await api.upload(zip);
appId
is the ID of the existing Web Store item (could be found in admin panel)
1// Any Readable stream or Buffer 2const zip = fs.createReadStream('./mypackage.zip'); 3// Result format is defined as IWebstoreResource in .d.ts file 4const result = await api.upload(zip, appId);
1// Result format is defined as IWebstoreResource in .d.ts file 2const result = await api.get(appId);
1// 'default' or 'trustedTesters', defined in PublishTarget enum in .d.ts file 2const target = 'default'; 3// Result format is defined as IPublishResponse in .d.ts file 4const result = await api.publish(appId, target);
Be aware of API's undocumented behaviour. For example, extension had a version = '1.10.0' Then we successfully published a new one with version = '1.20.0' (status = 'OK') 'get upload' request returns version '1.20.0' after it. But this version is still in publishing progress Now we are publishing '1.30.0' but 'publish' and request fails with 500 error, but (!) actually Our version have been accepted, and after some time out extension increases it's version to '1.30.0'!
1const result = await api.getLicenses(appId, userId);
1const result = await api.getUserLicenses(appId);
1const result = await api.getPayments(itemId);
This feature is experimental because of API is not documented
1// A bit ugly, looks better if you use TypeScript :) 2const downloadCrx = require('typed-chrome-webstore-api').DownloadCrx.downloadCrx; 3const fs = require('fs'); 4 5const fstream = fs.createWriteStream('file.crx'); 6const readStream = await downloadCrx('extensionId'); 7readStream.pipe(fstream);
downloadCrx()
also accepts additional options, look at downloadCrx.d.ts
file for details
MIT License
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
4 existing vulnerabilities detected
Details
Reason
Found 0/20 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
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
detected GitHub workflow tokens with excessive permissions
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
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
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