@jskit-ai/database-runtime
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Intentional env-merging pattern in a service provider config factory; not malicious exfiltration. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private scoped monorepo package; missing metadata is expected for internal packages. | ai |
Versions (showing 51 of 80)
| Version | Deps | Published |
|---|---|---|
| 0.1.85 | 1 / 0 | |
| 0.1.84 | 1 / 0 | |
| 0.1.83 | 1 / 0 | |
| 0.1.82 | 1 / 0 | |
| 0.1.81 | 1 / 0 | |
| 0.1.80 | 1 / 0 | |
| 0.1.79 | 1 / 0 | |
| 0.1.78 | 1 / 0 | |
| 0.1.77 | 1 / 0 | |
| 0.1.76 | 1 / 0 | |
| 0.1.75 | 1 / 0 | |
| 0.1.74 | 1 / 0 | |
| 0.1.73 | 1 / 0 | |
| 0.1.72 | 1 / 0 | |
| 0.1.71 | 1 / 0 | |
| 0.1.70 | 1 / 0 | |
| 0.1.69 | 1 / 0 | |
| 0.1.68 | 1 / 0 | |
| 0.1.67 | 1 / 0 | |
| 0.1.66 | 1 / 0 | |
| 0.1.65 | 1 / 0 | |
| 0.1.64 | 1 / 0 | |
| 0.1.63 | 1 / 0 | |
| 0.1.62 | 1 / 0 | |
| 0.1.61 | 1 / 0 | |
| 0.1.60 | 1 / 0 | |
| 0.1.59 | 1 / 0 | |
| 0.1.58 | 1 / 0 | |
| 0.1.57 | 1 / 0 | |
| 0.1.56 | 1 / 0 | |
| 0.1.55 | 1 / 0 | |
| 0.1.54 | 1 / 0 | |
| 0.1.53 | 1 / 0 | |
| 0.1.52 | 1 / 0 | |
| 0.1.51 | 1 / 0 | |
| 0.1.50 | 1 / 0 | |
| 0.1.49 | 1 / 0 | |
| 0.1.48 | 1 / 0 | |
| 0.1.47 | 1 / 0 | |
| 0.1.46 | 1 / 0 | |
| 0.1.45 | 1 / 0 | |
| 0.1.44 | 1 / 0 | |
| 0.1.43 | 1 / 0 | |
| 0.1.42 | 1 / 0 | |
| 0.1.41 | 1 / 0 | |
| 0.1.40 | 1 / 0 | |
| 0.1.39 | 1 / 0 | |
| 0.1.38 | 1 / 0 | |
| 0.1.37 | 1 / 0 | |
| 0.1.36 | 1 / 0 | |
| 0.1.35 | 1 / 0 |
v0.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.66
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.65
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.64
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.63
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.62
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.61
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.60
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.59
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.58
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.57
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.56
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.55
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.54
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.53
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.52
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.51
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.50
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.49
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.48
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.47
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.46
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
2 findingsSpreading entire process.env into an object — may capture all secrets 15 | const envFromScope = scope?.has?.("jskit.env") ? scope.make("jskit.env") : {}; 16 | const source = envFromScope && typeof envFromScope === "object" ? envFromScope : {}; > 17 | return { 18 | ...process.env, 19 | ...source
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.