← Home

@ngrok/ngrok

npm Repository Homepage
13
Versions
—
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

inconshreveablecody.jseng-npm-botpshaftonbmpngrok

Keywords

ngroknodejsingressnetworking

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-execsync AI (semgrep): Used solely for musl/glibc detection to load correct native binary; stable pattern for this napi-rs package. ai
semgrep semgrep:child-process-import AI (semgrep): Same musl-detection use case; not a security concern for this package. ai

Versions (showing 13 of 13)

Version Deps Published
1.7.0 0 / 14
1.6.1 0 / 14
1.6.0 0 / 14
1.5.2 0 / 14
1.5.1 0 / 14
1.5.0 0 / 14
1.4.1 0 / 9
1.4.0 0 / 9
1.3.0 0 / 9
1.2.0 0 / 9
1.1.1 0 / 9
1.1.0 0 / 9
1.0.0 0 / 9

v1.5.0

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: bobzilladev → eng-npm-bot (on 2025-04-15, known maintainer) provenance

This version was published by a different npm account (eng-npm-bot) than the most recent previously approved version (bobzilladev) on 2025-04-15, but eng-npm-bot 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.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.