snowflake-sdk
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Canonical Snowflake SDK with 84 published versions and 1.9M weekly downloads; dormancy gap is not indicative of takeover for this well-known package. | ai | |
| dependencies | unvetted-dep:binascii | AI (dependencies): Small stable encoding utility pinned to 0.0.2; consistent with SDK's data encoding needs. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Documented JSON column variant parser; pattern is stable across versions of this connector. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Used for OCSP certificate parsing in cert_util.js; legitimate cryptographic use, not payload hiding. | ai | |
| phantom-deps | phantom-dep:wiremock-rest-client | AI (phantom-deps): wiremock-rest-client is a test/mock utility; phantom-dep finding is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Snowflake SDK is a well-established, official corporate package. Lack of Sigstore provenance is common and not a meaningful risk signal for this package. | ai | |
| dependencies | unvetted-dep:expand-tilde | AI (dependencies): expand-tilde is a well-known small utility for resolving ~ in file paths; its use in a database driver for config path resolution is benign and stable. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Binaries are NAPI-RS native modules (sf_mini_core) for the Snowflake connector, built with @napi-rs/cli as declared in package.json. Legitimate multi-platform native module distribution for an established enterprise SDK. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 32 / 20 | |
| 3.0.0 | 29 / 20 | |
| 2.4.3 | 32 / 20 | |
| 2.4.2 | 32 / 20 | |
| 2.4.1 | 32 / 20 | |
| 2.4.0 | 34 / 20 | |
| 2.3.6 | 34 / 20 | |
| 2.3.5 | 35 / 20 | |
| 2.3.4 | 35 / 20 | |
| 2.3.3 | 35 / 20 | |
| 2.3.2 | 36 / 20 | |
| 2.3.1 | 36 / 19 | |
| 2.3.0 | 35 / 19 | |
| 2.2.0 | 38 / 19 | |
| 2.1.3 | 38 / 19 | |
| 2.1.2 | 38 / 19 | |
| 2.1.1 | 38 / 20 | |
| 2.1.0 | 32 / 9 | |
| 2.0.4 | 30 / 10 |
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.