belter Apache-2.0 51 versions

belter

npm Repository Homepage

Utilities.

51

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

gregjopabluepnumewsbrunsonmnicptelizabethmvfrnuzzi

Keywords

browserutilitiestools

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file-transition:dist/mylibrary.js	AI (source-diff): Webpack bundle boilerplate, no actual dropper behavior; stable false positive for this bundled lib.	ai	2026/07/27
source-diff	net-exec-file-transition:dist/mylibrary.min.js	AI (source-diff): Minified bundle of same file; same false positive pattern.	ai	2026/07/27
publish-pattern	new-deps-added	AI (publish-pattern): Base64 is a trivial well-known encoding utility, not a supply-chain risk.	ai	2026/07/27
semgrep	semgrep:base64-decode	AI (semgrep): The base64 decode in src/util.js is a transparent utility function (Buffer.from(str,'base64').toString('utf8')); no obfuscation or payload hiding. Stable false positive for this package.	ai	2026/04/21

Versions (showing 51 of 169)

View all versions

Version	Deps	Published
1.0.189	3 / 3	2022-01-31
1.0.187	3 / 3	2022-01-26
1.0.186	3 / 3	2022-01-19
1.0.185	3 / 3	2022-01-18
1.0.184	3 / 3	2022-01-14
1.0.183	3 / 3	2022-01-10
1.0.182	3 / 3	2022-01-10
1.0.181	3 / 3	2022-01-10
1.0.180	3 / 3	2022-01-10
1.0.177	3 / 3	2021-09-22
1.0.176	3 / 3	2021-09-22
1.0.175	3 / 3	2021-09-15
1.0.174	3 / 3	2021-09-15
1.0.173	3 / 3	2021-07-19
1.0.172	3 / 3	2021-07-19
1.0.171	3 / 3	2021-07-15
1.0.170	3 / 3	2021-05-24
1.0.169	3 / 3	2021-05-18
1.0.168	3 / 3	2021-05-17
1.0.167	3 / 3	2021-05-13
1.0.166	3 / 3	2021-05-13
1.0.165	3 / 3	2021-04-22
1.0.164	3 / 3	2021-04-15
1.0.163	3 / 3	2021-03-29
1.0.162	3 / 3	2021-03-26
1.0.161	3 / 3	2021-03-23
1.0.160	3 / 3	2021-03-16
1.0.159	3 / 3	2021-03-09
1.0.158	3 / 3	2021-03-08
1.0.157	3 / 3	2021-03-05
1.0.155	3 / 3	2021-03-04
1.0.152	3 / 3	2021-02-09
1.0.151	3 / 3	2021-02-09
1.0.150	3 / 3	2021-01-26
1.0.149	3 / 3	2021-01-15
1.0.148	3 / 3	2020-12-19
1.0.147	3 / 3	2020-12-17
1.0.146	3 / 3	2020-12-09
1.0.145	3 / 3	2020-11-29
1.0.144	3 / 3	2020-11-05
1.0.142	3 / 3	2020-10-12
1.0.141	3 / 3	2020-10-05
1.0.140	3 / 3	2020-10-02
1.0.139	3 / 3	2020-09-30
1.0.138	3 / 3	2020-09-30
1.0.137	3 / 3	2020-09-30
1.0.136	3 / 3	2020-09-30
1.0.135	3 / 3	2020-09-30
1.0.134	3 / 3	2020-09-29
1.0.133	3 / 3	2020-09-28
1.0.132	3 / 3	2020-09-28

v1.0.189

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: gregjopa → mnicpt (on 2022-01-31, known maintainer) provenance

This version was published by a different npm account (mnicpt) than the most recent previously approved version (gregjopa) on 2022-01-31, but mnicpt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.187

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → gregjopa (on 2022-01-26, known maintainer) provenance

This version was published by a different npm account (gregjopa) than the most recent previously approved version (bluepnume) on 2022-01-26, but gregjopa is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.186

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → gregjopa (on 2022-01-19, known maintainer) provenance

This version was published by a different npm account (gregjopa) than the most recent previously approved version (bluepnume) on 2022-01-19, but gregjopa is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.185

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mnicpt → bluepnume (on 2022-01-18, known maintainer) provenance

This version was published by a different npm account (bluepnume) than the most recent previously approved version (mnicpt) on 2022-01-18, but bluepnume is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.184

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.183

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.182

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.181

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.180

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mnicpt → gregjopa (on 2022-01-10, known maintainer) provenance

This version was published by a different npm account (gregjopa) than the most recent previously approved version (mnicpt) on 2022-01-10, but gregjopa is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.177

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.176

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → mnicpt (on 2021-09-22, known maintainer) provenance

This version was published by a different npm account (mnicpt) than the most recent previously approved version (bluepnume) on 2021-09-22, but mnicpt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.175

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → gregjopa (on 2021-09-15, known maintainer) provenance

This version was published by a different npm account (gregjopa) than the most recent previously approved version (bluepnume) on 2021-09-15, but gregjopa is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.174

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.172

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: gregjopa → bluepnume (on 2021-07-19, known maintainer) provenance

This version was published by a different npm account (bluepnume) than the most recent previously approved version (gregjopa) on 2021-07-19, but bluepnume is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.171

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: gregjopa → bluepnume (on 2021-07-15, known maintainer) provenance

This version was published by a different npm account (bluepnume) than the most recent previously approved version (gregjopa) on 2021-07-15, but bluepnume is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.170

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → gregjopa (on 2021-05-24, known maintainer) provenance

This version was published by a different npm account (gregjopa) than the most recent previously approved version (bluepnume) on 2021-05-24, but gregjopa is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.169

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.168

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.167

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → gregjopa (on 2021-05-13, known maintainer) provenance

This version was published by a different npm account (gregjopa) than the most recent previously approved version (bluepnume) on 2021-05-13, but gregjopa is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.166

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mnicpt → bluepnume (on 2021-05-13, known maintainer) provenance

This version was published by a different npm account (bluepnume) than the most recent previously approved version (mnicpt) on 2021-05-13, but bluepnume is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.165

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mnicpt → bluepnume (on 2021-04-22, known maintainer) provenance

This version was published by a different npm account (bluepnume) than the most recent previously approved version (mnicpt) on 2021-04-22, but bluepnume is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.164

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.163

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.162

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → mnicpt (on 2021-03-26, known maintainer) provenance

This version was published by a different npm account (mnicpt) than the most recent previously approved version (bluepnume) on 2021-03-26, but mnicpt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.161

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → mnicpt (on 2021-03-23, known maintainer) provenance

This version was published by a different npm account (mnicpt) than the most recent previously approved version (bluepnume) on 2021-03-23, but mnicpt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.160

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mnicpt → bluepnume (on 2021-03-16, known maintainer) provenance

This version was published by a different npm account (bluepnume) than the most recent previously approved version (mnicpt) on 2021-03-16, but bluepnume is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.159

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.158

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → mnicpt (on 2021-03-08, known maintainer) provenance

This version was published by a different npm account (mnicpt) than the most recent previously approved version (bluepnume) on 2021-03-08, but mnicpt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.157

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bluepnume → mnicpt (on 2021-03-05, known maintainer) provenance

This version was published by a different npm account (mnicpt) than the most recent previously approved version (bluepnume) on 2021-03-05, but mnicpt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.155

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.152

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.151

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.150

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.149

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.148

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.147

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.146

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.145

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.144

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.142

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.141

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.140

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.139

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.138

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.137

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.136

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.135

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.134

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.133

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.132

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.