← Home

serverless-offline

npm Repository Homepage
19
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

medikoodheraultpgrzesikmohokh67daniel0707dnalborczykdmelosantosmazurdorian

Keywords

serverlessserverless frameworkserverless localserverless offlineserverless pluginawsamazon web servicesapi gatewayhttplambdaschedulewebsocket

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Intentional: local Lambda emulator spreads process.env into child process env; this is the documented behavior for localEnvironment mode. ai
semgrep semgrep:base64-decode AI (semgrep): Standard ALB response body decoding; not a malicious payload pattern. ai
semgrep semgrep:dynamic-require AI (semgrep): Lambda handler loader by design; loads user-specified handler files at runtime. ai
phantom-deps phantom-dep:tsx AI (phantom-deps): Referenced in config files only; stable false positive for this package. ai
phantom-deps phantom-dep:nock AI (phantom-deps): Referenced in config files only; stable false positive for this package. ai
phantom-deps phantom-dep:tree-kill AI (phantom-deps): Referenced in config files only; stable false positive for this package. ai

Versions (showing 19 of 19)

Version Deps Published
14.7.4 25 / 13
14.7.3 25 / 13
14.7.2 25 / 13
14.7.1 25 / 13
14.7.0 25 / 13
14.6.0 25 / 13
14.5.0 26 / 13
14.4.0 26 / 13
14.3.4 25 / 13
14.3.3 25 / 13
14.3.2 25 / 13
14.3.1 25 / 13
14.3.0 25 / 13
14.2.0 25 / 13
14.1.1 25 / 13
14.1.0 24 / 13
14.0.0 24 / 13
13.10.1 22 / 13
13.10.0 22 / 13

v14.4.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: mazurdorian → dherault (on 2024-12-09, known maintainer) provenance

This version was published by a different npm account (dherault) than the most recent previously approved version (mazurdorian) on 2024-12-09, but dherault 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.

v14.3.4

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: mazurdorian → dherault (on 2024-11-06, known maintainer) provenance

This version was published by a different npm account (dherault) than the most recent previously approved version (mazurdorian) on 2024-11-06, but dherault 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.

v14.3.3

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: dherault → mazurdorian (on 2024-10-17, known maintainer) provenance

This version was published by a different npm account (mazurdorian) than the most recent previously approved version (dherault) on 2024-10-17, but mazurdorian 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.

v14.3.2

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: dherault → mazurdorian (on 2024-09-23, known maintainer) provenance

This version was published by a different npm account (mazurdorian) than the most recent previously approved version (dherault) on 2024-09-23, but mazurdorian 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.

v14.3.1

1 finding
LOW No provenance attestation provenance

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

v14.3.0

1 finding
LOW No provenance attestation provenance

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

v14.2.0

1 finding
LOW No provenance attestation provenance

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

v14.1.1

1 finding
LOW No provenance attestation provenance

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

v14.1.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: mazurdorian → dherault (on 2024-08-17, known maintainer) provenance

This version was published by a different npm account (dherault) than the most recent previously approved version (mazurdorian) on 2024-08-17, but dherault 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.

v14.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.