Gathering detailed insights and metrics for gulp-jscrambler
Gathering detailed insights and metrics for gulp-jscrambler
Gathering detailed insights and metrics for gulp-jscrambler
Gathering detailed insights and metrics for gulp-jscrambler
Monorepo of Jscrambler's Javascript Client and Integrations
npm install gulp-jscrambler
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (99.71%)
Shell (0.29%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
154 Stars
1,116 Commits
31 Forks
15 Watchers
9 Branches
27 Contributors
Updated on Jul 09, 2025
Latest Version
8.5.25
Package Id
gulp-jscrambler@8.5.25
Unpacked Size
8.20 kB
Size
3.56 kB
File Count
4
NPM Version
10.8.2
Node Version
18.20.8
Published on
Jul 09, 2025
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
5
5
Jscrambler Code Integrity is a JavaScript protection technology for Web and Mobile Applications. Its main purpose is to enable JavaScript applications to become self-defensive and resilient to tampering and reverse engineering.
If you're looking to gain control over third-party tags and achieve PCI DSS compliance please refer to Jscrambler Webpage Integrity.
Add obfuscation to your build process with gulp and gulp-jscrambler.
The version's compatibility table match your Jscrambler Version with the Jscrambler Gulp Client. Please make sure you install the right version, otherwise some functionalities might not work properly.
Jscrambler Version | Client and Integrations |
---|---|
<= 7.1 | <= 5.x.x |
>= 7.2 | >= 6.0.0 |
Install with npm.
npm install -D gulp-jscrambler
Option -D
will make sure it is installed as a devDependency
.
In order to start using gulp-jscrambler you will need to add a new task to your project gulpfile.js
. This task will be responsible for protecting your application with Jscrambler.
Here's an example of how Jscrambler task should look like:
1const gulp = require('gulp'); 2const jscrambler = require('gulp-jscrambler'); 3 4function enable(filesSrc) { 5 if (filesSrc.length === 0) { 6 return false; 7 } 8 9 return true; 10} 11 12gulp.task('default', function (done) { 13 gulp 14 .src('app/**/*.js') 15 .pipe(jscrambler({ 16 keys: { 17 accessKey: 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', 18 secretKey: 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' 19 }, 20 applicationId: 'XXXXXXXXXXXX', 21 enable, 22 params: [ 23 { 24 name: 'whitespaceRemoval' 25 }, 26 { 27 name: 'stringSplitting' 28 } 29 ] 30 })) 31 .pipe(gulp.dest('dist/')) 32 .on('end', done); 33});
You will need your credentials and Application ID in order to protect your application.
Navigate to your Settings page and grab your accessKey
and secretKey
at the API Credentials section.
Your applicationId
can be found inside your application page just below your application name. Click the copy to clipboard icon to copy the applicationId
.
You can also grab your current configuration on your application page. This will download a .json
file containing a valid configuration with your currently selected options.
Keep in mind that the params
object is optional and if it is not provided we will use your previous configuration.
The enable
object is an optional function (returns true by default) that will allow to manipulate the files sources and decide if you want to protect them (returning true) or skip (returning false). The example provided before is a use case that will skip the Jscrambler protection when there isn't any files on source.
You can find some working examples here.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
Found 7/9 approved changesets -- score normalized to 7
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
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
Reason
27 existing vulnerabilities detected
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