@rip-lang/db MIT 18 versions

@rip-lang/db

npm Repository Homepage

DuckDB server with official DuckDB UI - pure Bun FFI

18

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

shreeve

Keywords

dbdatabaseduckdbduckdb-harborsqlhttpclientmcpbunrip

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped @rip-lang/db package; Levenshtein match to 'pg' is coincidental, not a squatting attempt.	ai	2026/04/29
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped @rip-lang/db package; Levenshtein match to 'qs' is coincidental, not a squatting attempt.	ai	2026/04/29
phantom-deps	phantom-dep:rip-lang	AI (phantom-deps): rip-lang is the runtime for .rip files; not directly imported via JS but legitimately required.	ai	2026/04/29
phantom-deps	phantom-dep:@rip-lang/server	AI (phantom-deps): Same-org dependency used by .rip source files, not JS imports; stable false positive for this package.	ai	2026/04/29

Versions (showing 18 of 118)

Version	Deps	Published
1.3.31	2 / 0	2026-02-27
1.3.30	2 / 0	2026-02-27
1.3.29	2 / 0	2026-02-27
1.3.28	2 / 0	2026-02-27
1.3.27	2 / 0	2026-02-27
1.3.26	2 / 0	2026-02-27
1.3.25	2 / 0	2026-02-27
1.3.24	2 / 0	2026-02-27
1.3.23	2 / 0	2026-02-27
1.3.22	2 / 0	2026-02-27
1.3.21	2 / 0	2026-02-27
1.3.20	2 / 0	2026-02-27
1.3.19	2 / 0	2026-02-26
1.3.18	2 / 0	2026-02-26
1.3.17	2 / 0	2026-02-26
1.3.16	2 / 0	2026-02-26
1.3.15	2 / 0	2026-02-25
1.3.14	2 / 0	2026-02-25

v1.3.31

1 finding

LOW No provenance attestation provenance

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

v1.3.30

1 finding

LOW No provenance attestation provenance

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

v1.3.29

1 finding

LOW No provenance attestation provenance

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

v1.3.28

1 finding

LOW No provenance attestation provenance

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

v1.3.27

1 finding

LOW No provenance attestation provenance

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

v1.3.26

1 finding

LOW No provenance attestation provenance

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

v1.3.25

1 finding

LOW No provenance attestation provenance

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

v1.3.24

1 finding

LOW No provenance attestation provenance

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

v1.3.23

1 finding

LOW No provenance attestation provenance

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

v1.3.22

1 finding

LOW No provenance attestation provenance

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

v1.3.21

1 finding

LOW No provenance attestation provenance

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

v1.3.20

1 finding

LOW No provenance attestation provenance

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

v1.3.19

1 finding

LOW No provenance attestation provenance

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

v1.3.18

1 finding

LOW No provenance attestation provenance

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

v1.3.17

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.

v1.3.16

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.

v1.3.15

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.

v1.3.14

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.