← Home

alasql

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

mathiasrwagershun

Keywords

SQLjavascriptdatabaseExcelXLSXXLSCSV

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:node-fetch AI (phantom-deps): Used conditionally for Node fetch polyfill in cross-env bundled code. ai
phantom-deps phantom-dep:dom-storage AI (phantom-deps): Node-side localStorage polyfill, used conditionally per environment. ai
phantom-deps phantom-dep:es6-promise AI (phantom-deps): Promise polyfill for older environments; conditional usage not scanned. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): 127.0.0.1 in a console.log for a local dev server; not a malicious raw-IP connection. ai

Versions (showing 18 of 18)

Version Deps Published
4.17.3 2 / 14
4.17.2 2 / 16
4.17.1 2 / 16
4.17.0 2 / 16
4.16.0 2 / 16
4.15.0 2 / 16
4.14.0 2 / 16
4.13.0 2 / 16
4.12.0 2 / 16
4.11.0 2 / 16
4.10.1 2 / 16
4.10.0 2 / 17
4.9.0 2 / 17
4.8.0 2 / 17
4.7.0 2 / 17
4.6.6 2 / 17
4.0.1 6 / 27
4.0.0 6 / 27

v4.17.0

1 finding
LOW No provenance attestation provenance

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

v4.16.0

1 finding
LOW No provenance attestation provenance

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

v4.15.0

1 finding
LOW No provenance attestation provenance

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

v4.14.0

1 finding
LOW No provenance attestation provenance

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

v4.13.0

1 finding
LOW No provenance attestation provenance

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

v4.12.0

1 finding
LOW No provenance attestation provenance

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

v4.11.0

1 finding
LOW No provenance attestation provenance

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

v4.10.1

1 finding
LOW No provenance attestation provenance

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

v4.10.0

1 finding
LOW No provenance attestation provenance

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

v4.9.0

1 finding
LOW No provenance attestation provenance

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

v4.8.0

1 finding
LOW No provenance attestation provenance

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

v4.7.0

1 finding
LOW No provenance attestation provenance

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

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

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