lightning No license 16 versions

lightning

npm Repository Homepage

16

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

alexbosworth

Keywords

grpclightning-networklnd

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@alexbosworth/blockchain	AI (dependencies): Same-author dependency from the package's own maintainer; stable pattern across versions.	ai	2026/05/13
dependencies	unvetted-dep:psbt	AI (dependencies): Part of alexbosworth's Lightning ecosystem; stable dependency pattern across versions.	ai	2026/05/02
dependencies	unvetted-dep:bolt07	AI (dependencies): Part of alexbosworth's Lightning ecosystem; stable dependency pattern across versions.	ai	2026/05/02
dependencies	unvetted-dep:bolt09	AI (dependencies): Part of alexbosworth's Lightning ecosystem; stable dependency pattern across versions.	ai	2026/05/02
dependencies	unvetted-dep:invoices	AI (dependencies): Part of alexbosworth's Lightning ecosystem; stable dependency pattern across versions.	ai	2026/05/02
dependencies	unvetted-dep:asyncjs-util	AI (dependencies): Utility package in alexbosworth's ecosystem; stable dependency pattern across versions.	ai	2026/05/02
semgrep	semgrep:base64-decode	AI (semgrep): Base64 used for macaroon parsing, standard LND auth pattern.	ai	2026/04/28
phantom-deps	phantom-dep:@types/ws	AI (phantom-deps): TypeScript type package; not directly imported by convention.	ai	2026/04/28
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): TypeScript type package; not directly imported by convention.	ai	2026/04/28
phantom-deps	phantom-dep:@types/request	AI (phantom-deps): TypeScript type package; not directly imported by convention.	ai	2026/04/28
semgrep	semgrep:hex-decode	AI (semgrep): Hex encoding/decoding is core to Bitcoin/LN protocol handling; not obfuscation.	ai	2026/04/28

Versions (showing 16 of 16)

Version	Deps	Published
12.1.0	14 / 2	2026-06-05
12.0.4	14 / 2	2026-05-29
12.0.3	14 / 2	2026-05-29
12.0.2	14 / 2	2026-05-22
12.0.1	14 / 2	2026-05-13
12.0.0	14 / 2	2026-05-11
11.1.0	14 / 2	2026-04-25
11.0.5	14 / 2	2026-04-17
11.0.4	14 / 2	2026-04-08
11.0.3	14 / 2	2026-03-07
11.0.2	14 / 2	2026-02-21
11.0.1	14 / 2	2026-02-12
11.0.0	14 / 2	2026-01-22
10.27.5	14 / 2	2025-12-13
10.27.4	14 / 2	2025-12-11
10.27.3	16 / 2	2025-11-25

v12.1.0

1 finding

LOW No provenance attestation provenance

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

v12.0.4

1 finding

LOW No provenance attestation provenance

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

v12.0.3

1 finding

LOW No provenance attestation provenance

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

v12.0.2

1 finding

LOW No provenance attestation provenance

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

v12.0.1

1 finding

LOW No provenance attestation provenance

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

v12.0.0

1 finding

LOW No provenance attestation provenance

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

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

v11.0.5

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.

v11.0.4

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.

v11.0.3

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.

v11.0.2

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.

v11.0.1

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.

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

v10.27.5

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.

v10.27.4

1 finding

LOW No provenance attestation provenance

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

v10.27.3

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.