← Home

sqlstring

npm Repository Homepage

Simple SQL escape and format for MySQL

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

Maintainers

sidoraresdougwilson

Keywords

sqlstringsqlescapesql escape

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transfer within mysqljs org; dougwilson is a well-known maintainer of the mysql ecosystem with 12+ years of npm history. ai
maintainer-change maintainer-added AI (maintainer-change): dougwilson and sidorares are established mysqljs maintainers; this is a known legitimate project transfer. ai
provenance no-provenance AI (provenance): Published in 2016, before Sigstore/provenance existed. Expected for packages of this era. ai

Versions (showing 10 of 10)

Version Deps Published
2.3.3 0 / 7
2.3.2 0 / 7
2.3.1 0 / 7
2.3.0 0 / 7
2.2.0 0 / 7
2.1.0 0 / 7
2.0.1 0 / 7
2.0.0 0 / 7
1.0.0 0 / 9
0.0.1 0 / 9

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

2 findings
HIGH Publisher changed: fengmk2 → dougwilson (on 2016-06-06) provenance

This version was published by a different npm account than previous versions on 2016-06-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

1 finding
INFO No provenance attestation provenance

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