
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Named for the Vulcanization process that turns polymers into more durable materials.
vulcanize
is available on npm. For maximium utility, vulcanize
should be installed globally.
sudo npm install -g vulcanize
This will install vulcanize
to /usr/local/bin/vulcanize
.
vulcanize index.html
At the simplest, vulcanize
only requires an html file as an argument. The optimized output file will be named
vulcanized.html
.
If you want to control the output name, use the -o
flag
vulcanize -o build.html index.html
Most URLs will be automatically adjusted by the vulcanizer.
--output
, -o
--verbose
, -v
--help
, -v
, -?
--config
--strip
, -s
--csp
<output file name>
.js)--inline
JSON file for additional options
{
"excludes": {
"imports": [
"regex-to-exclude"
]
}
}
Say we have three html files: index.html
, x-app.html
, and x-dep.html
.
index.html:
<!DOCTYPE html>
<link rel="import" href="app.html">
<x-app></x-app>
app.html:
<link rel="import" href="path/to/x-dep.html">
<polymer-element name="x-app">
<template>
<x-dep></x-dep>
</template>
<script>Polymer('x-app')</script>
</polymer-element>
x-dep.html:
<polymer-element name="x-dep">
<template>
<img src="x-dep-icon.jpg">
</template>
<script>
Polymer('x-dep');
</script>
</polymer-element>
Running vulcan on index.html
, and specifying build.html
as the output:
vulcanize -o build.html index.html
Will result in build.html
that appears as so:
<!DOCTYPE html>
<polymer-element name="x-dep" assetpath="path/to/">
<template>
<img src="path/to/x-dep-icon.jpg">
</template>
<script>
Polymer('x-dep');
</script>
</polymer-element>
<polymer-element name="x-app" assetpath="">
<template>
<x-dep></x-dep>
</template>
<script>
Polymer('x-app');
</script>
</polymer-element>
<x-app></x-app>
Content Security Policy, or CSP, is a Javascript security model that aims to prevent XSS and other attacks. In so doing, it prohibits the use of inline scripts.
To help automate the use of Polymer element registration with CSP, the --csp
flag to vulcan will remove all scripts
from the HTML Imports and place their contents into an output javascript file.
Using the previous example, the output from vulcanize --csp -o build.html index.html
will be
build.html:
<!DOCTYPE html>
<polymer-element name="x-dep" assetpath="path/to/">
<template>
<img src="path/to/x-dep-icon.jpg">
</template>
</polymer-element>
<polymer-element name="x-app" assetpath="">
<template>
<x-dep></x-dep>
</template>
</polymer-element>
<script src="build.js"></script>
<x-app></x-app>
build.js:
Polymer('x-dep');
Polymer('x-app');
FAQs
Process Web Components into one output file
We found that vulcanize 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.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.