
Product
Introducing Pull Request Stories to Help Security Teams Track Supply Chain Risks
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.
Deploy your ./dist/
directory to the Livefyre CDN.
It will read from the name
and version
in your package.json
You will need to set the following environment variables
export LF_CDN_S3_KEY='...'
export LF_CDN_S3_SECRET='...'
Install with npm.
npm install -g git+ssh://git@github.com:Livefyre/lfcdn
Note the -g
. It will add lfcdn
to your PATH.
lfcdn -h
Usage: lfcdn -e {dev|qa|staging|prod} -c [/path/to/config.json] [--reporter (url|none)]
--reporter urls
will print URLs to stdout for each file
lfcdn -c [/path/to/config.json]
Load config from a JSON config file. Supported config options:
dir
- S3 key to deploy files to. Defaults to a path derrived from the name
in package.json
lfcdn -e {dev|qa|staging|prod}
Environment to deploy to. Defaults to dev
.
livefyre-cdn-dev: deploying streamhub-sdk
[gulp] [cache] libs/streamhub-sdk/2.7.5/streamhub-sdk.min.css
[gulp] [cache] libs/streamhub-sdk/2.7.5/streamhub-sdk.min.js
[gulp] [cache] libs/streamhub-sdk/2.7.5/streamhub-sdk.min.js.map
lfcdn -f
By default lfcdn will not update published files. One can, however, overwrite published files with the force option.
FAQs
Deploy your `./dist/` directory to the Livefyre CDN.
We found that lfcdn demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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.
Product
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.
Research
/Security News
npm author Qix’s account was compromised, with malicious versions of popular packages like chalk-template, color-convert, and strip-ansi published.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.