← Home

node-sql-parser

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

taozhi8833998

Keywords

sqlsql-parserparsernodenodejsnode-parsernode-sql-parserastsql-ast

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): PEG.js-generated parser UMD bundle; new Function() is standard in generated parser output for this package. ai
dependencies unvetted-dep:@types/pegjs AI (dependencies): @types/pegjs is a benign TypeScript type definition package for PEG.js; stable runtime dep for TypeScript consumers of node-sql-parser. ai
phantom-deps phantom-dep:@types/pegjs AI (phantom-deps): @types/* packages are loaded by TypeScript convention, not via explicit imports; phantom-dep finding is a stable false positive for this package. ai

Versions (showing 18 of 18)

Version Deps Published
5.4.0 2 / 32
5.3.13 2 / 32
5.3.12 2 / 32
5.3.11 2 / 33
5.3.10 2 / 33
5.3.9 2 / 33
5.3.8 2 / 33
5.3.7 2 / 33
5.3.6 2 / 33
5.3.5 2 / 33
5.3.4 2 / 33
5.3.3 2 / 33
5.3.2 2 / 33
5.3.1 2 / 33
5.3.0 2 / 33
5.2.0 2 / 33
5.1.0 2 / 33
5.0.0 2 / 32

v5.3.8

1 finding
LOW No provenance attestation provenance

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

v5.3.7

1 finding
LOW No provenance attestation provenance

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

v5.3.6

1 finding
LOW No provenance attestation provenance

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

v5.3.5

1 finding
LOW No provenance attestation provenance

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

v5.3.4

1 finding
LOW No provenance attestation provenance

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

v5.3.3

1 finding
LOW No provenance attestation provenance

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

v5.3.2

1 finding
LOW No provenance attestation provenance

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

v5.3.1

1 finding
LOW No provenance attestation provenance

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

v5.3.0

1 finding
LOW No provenance attestation provenance

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

v5.2.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.

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

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