Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
ember-source-channel-url
Advanced tools
Determine the URL to a given Ember channels (beta, canary, etc) latest tarball.
Retrieve a URL that can be used to reference a tarball representing the latest
ember-source
build for that channel.
npx ember-source-channel-url canary
Will print out:
The URL for the latest tarball from ember-source's canary channel is:
https://s3.amazonaws.com/builds.emberjs.com/canary/shas/<RANDOM SHA HERE>.tgz
If you'd like to update ember-source
in your package.json
with the new URL, you can use the --write
option:
npx ember-source-channel-url canary --write
const getURLFor = require('ember-source-channel-url');
getURLFor('canary').then((url) => {
// use the URL here
});
FAQs
Determine the URL to a given Ember channels (beta, canary, etc) latest tarball.
The npm package ember-source-channel-url receives a total of 83,882 weekly downloads. As such, ember-source-channel-url popularity was classified as popular.
We found that ember-source-channel-url demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.