← Home

luacheck-browserify

npm Repository Homepage

Luacheck in browser

28
Versions
MIT
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

bhsd

Keywords

lualuachecklintlinterbrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/es8.min.js AI (source-diff): Minified esbuild bundle with base64 WASM decoder; expected for a browser-targeted Lua runtime package. ai
source-diff encoded-string-file:dist/index.min.js AI (source-diff): Same esbuild bundle pattern; wasmoon WASM payload is the documented core of this package. ai

Versions (showing 28 of 28)

Version Deps Published
1.0.0 0 / 11
0.11.1 0 / 13
0.11.0 0 / 23
0.10.1 0 / 23
0.10.0 0 / 23
0.9.2 0 / 23
0.9.1 0 / 23
0.9.0 0 / 22
0.8.2 0 / 21
0.8.1 0 / 21
0.8.0 0 / 21
0.7.1 0 / 21
0.6.2 0 / 21
0.6.1 0 / 21
0.6.0 0 / 21
0.5.2 0 / 21
0.5.1 0 / 21
0.5.0 0 / 27
0.4.0 0 / 27
0.3.1 0 / 26
0.3.0 0 / 26
0.2.3 0 / 26
0.2.2 0 / 26
0.2.1 0 / 23
0.2.0 0 / 23
0.1.1 0 / 23
0.1.0 0 / 23
0.0.3 0 / 23

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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

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