Gathering detailed insights and metrics for gorilla-build
Gathering detailed insights and metrics for gorilla-build
Gathering detailed insights and metrics for gorilla-build
Gathering detailed insights and metrics for gorilla-build
npm install gorilla-build
Typescript
Module System
Node Version
NPM Version
TypeScript (95.7%)
JavaScript (3.84%)
Shell (0.47%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
17 Stars
323 Commits
1 Watchers
7 Branches
1 Contributors
Updated on Feb 20, 2025
Latest Version
0.1.16
Package Id
gorilla-build@0.1.16
Unpacked Size
39.62 kB
Size
20.99 kB
File Count
28
NPM Version
8.3.1
Node Version
17.4.0
Published on
Jan 17, 2023
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
🙈 🙉 🙊
🍌 GreaseMonkey · TamperMonkey 🍌
Gorilla is a blazing fast, TypeScript build tool for creating better GreaseMonkey scripts. It handles the complex build chain, so you don't have to.
helper.ts
1export const hello = (name:string) => { 2 console.log(`Hello ${name}!`); 3}
main.ts
1import { hello } from './helper'; 2 3hello('world');
package.json
1... 2"scripts": { 3 "build": "gorilla --input ./main.ts --output ./script.user.js" 4 }, 5...
script.user.js
1// ==UserScript== 2// @name New Userscript 3// @namespace http://tampermonkey.net/ 4// @version 0.1 5// @description Gorilla-built, rock-solid, Monkey script 6// @updateURL 7// @downloadURL 8// @author You 9// @include https://** 10// 11// Created with love using Gorilla 12// ==/UserScript== 13 14(function () { 15 'use strict'; 16 17 function greet(name) { 18 console.log(`Hello, ${name}!`); 19 } 20 21 greet("This is a greeting"); 22 23}());
You can find a collection of samples, here.
--help
)Display help menu.
eg.
gorilla --help
--input, -i
)The input handler for your script.
Note: While not required, Gorilla recommends writing your scripts in TypeScript
.
eg.
gorilla --input ./my-input-file.ts ...
--output, -o
)The input handler for your script.
Note: While not required, GreaseMonkey scripts should end with .user.js
.
eg.
gorilla --output ./my-script.user.js ...
--config, -c
)JSON input Gorilla config including GreaseMonkey metadata block data.
eg.
gorilla --config ./my-config.json ...
--quiet, -q
)Hide all warning messages.
eg.
gorilla --quiet true ...
The config is based off of the officially supported Metadata Block items found here: https://wiki.greasespot.net/Metadata_Block
The following JSON keys are supported by GreaseMonkey:
author
- (string
) - Author of the scriptdescription
- (string
) - Description of the scriptexclude
- (string[]
) - URLs to exclude the script fromgrant
- (string[]
) - Permissions to grant to the scripticon
- (string
) - Icon for the scriptinclude
- (string[]
) - URLs to include the script inmatch
- (string[]
) - URLs to match the script inname
- (string
) - Name of the scriptnamespace
- (string
) - Namespace of the scriptnoframes
- (string
) - Whether or not to run in framesrequire
- (string[]
) - Scripts to include within the scriptresource
- (string[]
) - Resources to include within the scriptversion
- (string
) - Version number of the scriptupdateURL
- (string
) - URL location for script updatesdownloadURL
- (string
) - URL location for script downloadThe config will be constructed by both the optional config
argument and with information from the package.json
file for
your current project. Some information will be take from the root of your package.json
(eg. author
, name
, etc.). Other information can be defined in a gorilla
key in your package.json
. For example:
...
"name": "This is my awesome script package.json!",
...
"gorilla": {
"include": ["this_key", "and this one"],
"updateURL": "this_url"
}
NOTE - any valid keys in the gorilla
will override anything else from the root package.json
!
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
dependency not pinned by hash detected -- score normalized to 1
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
Found 0/3 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
17 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-14
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