Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
typed-chrome-webstore-api
Advanced tools
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:
const fetchToken = require('typed-chrome-webstore-api').fetchToken;
const token = fetchToken('clientId', 'clientSecret', 'refreshToken');
Then create WebstoreApi
instance initialized with token:
const WebstoreApi = require('typed-chrome-webstore-api').WebstoreApi;
const api = new WebstoreApi(token);
// Any Readable stream or Buffer
const zip = fs.createReadStream('./mypackage.zip');
// Result format is defined as IWebstoreResource in d.ts file
const result = await api.upload(zip);
appId
is the ID of the existing Web Store item (could be found in admin panel)
// Any Readable stream or Buffer
const zip = fs.createReadStream('./mypackage.zip');
// Result format is defined as IWebstoreResource in .d.ts file
const result = await api.upload(zip, appId);
// Result format is defined as IWebstoreResource in .d.ts file
const result = await api.get(appId);
// 'default' or 'trustedTesters', defined in PublishTarget enum in .d.ts file
const target = 'default';
// Result format is defined as IPublishResponse in .d.ts file
const 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'!
const result = await api.getLicenses(appId, userId);
const result = await api.getUserLicenses(appId);
const result = await api.getPayments(itemId);
This feature is experimental because of API is not documented
// A bit ugly, looks better if you use TypeScript :)
const downloadCrx = require('typed-chrome-webstore-api').DownloadCrx.downloadCrx;
const fs = require('fs');
const fstream = fs.createWriteStream('file.crx');
const readStream = await downloadCrx('extensionId');
readStream.pipe(fstream);
downloadCrx()
also accepts additional options, look at downloadCrx.d.ts
file for details
MIT License
FAQs
Typed Chrome Webstore API to upload/publish extensions
We found that typed-chrome-webstore-api demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.