← Home

@jskit-ai/auth-provider-supabase-core

npm
85
Versions
—
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

mercmobily

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): env-spread in an auth service provider config builder is a code-quality issue, not malware; stable pattern for this package. ai

Versions (showing 85 of 85)

Version Deps Published
0.1.90 6 / 0
0.1.89 6 / 0
0.1.88 6 / 0
0.1.87 6 / 0
0.1.86 6 / 0
0.1.85 6 / 0
0.1.84 6 / 0
0.1.83 6 / 0
0.1.82 6 / 0
0.1.81 6 / 0
0.1.80 6 / 0
0.1.79 6 / 0
0.1.78 6 / 0
0.1.77 6 / 0
0.1.76 6 / 0
0.1.75 6 / 0
0.1.74 6 / 0
0.1.73 6 / 0
0.1.72 6 / 0
0.1.71 6 / 0
0.1.70 6 / 0
0.1.69 6 / 0
0.1.68 6 / 0
0.1.67 6 / 0
0.1.66 6 / 0
0.1.65 6 / 0
0.1.64 6 / 0
0.1.63 6 / 0
0.1.62 6 / 0
0.1.61 6 / 0
0.1.60 6 / 0
0.1.59 6 / 0
0.1.58 5 / 0
0.1.57 5 / 0
0.1.56 5 / 0
0.1.55 5 / 0
0.1.54 4 / 0
0.1.53 4 / 0
0.1.52 4 / 0
0.1.51 4 / 0
0.1.50 4 / 0
0.1.49 4 / 0
0.1.48 4 / 0
0.1.47 4 / 0
0.1.46 4 / 0
0.1.45 4 / 0
0.1.44 4 / 0
0.1.43 4 / 0
0.1.42 4 / 0
0.1.41 4 / 0
0.1.40 4 / 0
0.1.39 4 / 0
0.1.38 4 / 0
0.1.37 4 / 0
0.1.36 4 / 0
0.1.35 4 / 0
0.1.34 4 / 0
0.1.33 4 / 0
0.1.32 4 / 0
0.1.31 4 / 0
0.1.30 4 / 0
0.1.29 4 / 0
0.1.28 4 / 0
0.1.27 4 / 0
0.1.25 4 / 0
0.1.24 4 / 0
0.1.23 4 / 0
0.1.22 4 / 0
0.1.21 4 / 0
0.1.20 4 / 0
0.1.19 4 / 0
0.1.18 4 / 0
0.1.17 4 / 0
0.1.16 4 / 0
0.1.15 4 / 0
0.1.14 4 / 0
0.1.13 4 / 0
0.1.12 4 / 0
0.1.11 4 / 0
0.1.10 4 / 0
0.1.9 4 / 0
0.1.8 4 / 0
0.1.7 4 / 0
0.1.5 4 / 0
0.1.4 4 / 0

v0.1.90

1 finding
LOW No provenance attestation provenance

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

v0.1.89

1 finding
LOW No provenance attestation provenance

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

v0.1.88

1 finding
LOW No provenance attestation provenance

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

v0.1.87

1 finding
LOW No provenance attestation provenance

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

v0.1.86

1 finding
LOW No provenance attestation provenance

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

v0.1.85

1 finding
LOW No provenance attestation provenance

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

v0.1.84

1 finding
LOW No provenance attestation provenance

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

v0.1.83

1 finding
LOW No provenance attestation provenance

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

v0.1.82

1 finding
LOW No provenance attestation provenance

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

v0.1.81

1 finding
LOW No provenance attestation provenance

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

v0.1.80

1 finding
LOW No provenance attestation provenance

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

v0.1.79

1 finding
LOW No provenance attestation provenance

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

v0.1.78

1 finding
LOW No provenance attestation provenance

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

v0.1.77

1 finding
LOW No provenance attestation provenance

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

v0.1.76

1 finding
LOW No provenance attestation provenance

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

v0.1.75

1 finding
LOW No provenance attestation provenance

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

v0.1.74

1 finding
LOW No provenance attestation provenance

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

v0.1.73

1 finding
LOW No provenance attestation provenance

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

v0.1.72

1 finding
LOW No provenance attestation provenance

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

v0.1.71

1 finding
LOW No provenance attestation provenance

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

v0.1.70

1 finding
LOW No provenance attestation provenance

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

v0.1.69

1 finding
LOW No provenance attestation provenance

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

v0.1.68

1 finding
LOW No provenance attestation provenance

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

v0.1.67

1 finding
LOW No provenance attestation provenance

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

v0.1.66

1 finding
LOW No provenance attestation provenance

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

v0.1.65

1 finding
LOW No provenance attestation provenance

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

v0.1.64

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 172 | > 173 | return { 174 | ...process.env, 175 | ...envFromDependencies

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.

v0.1.63

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 172 | > 173 | return { 174 | ...process.env, 175 | ...envFromDependencies

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.

v0.1.62

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 172 | > 173 | return { 174 | ...process.env, 175 | ...envFromDependencies

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.

v0.1.61

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 172 | > 173 | return { 174 | ...process.env, 175 | ...envFromDependencies

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.

v0.1.60

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 172 | > 173 | return { 174 | ...process.env, 175 | ...envFromDependencies

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.

v0.1.59

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 172 | > 173 | return { 174 | ...process.env, 175 | ...envFromDependencies

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.

v0.1.58

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 172 | > 173 | return { 174 | ...process.env, 175 | ...envFromDependencies

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.

v0.1.57

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 172 | > 173 | return { 174 | ...process.env, 175 | ...envFromDependencies

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.

v0.1.56

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:172 semgrep

Spreading entire process.env into an object — may capture all secrets 170 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 171 | > 172 | return { 173 | ...process.env, 174 | ...envFromDependencies

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.

v0.1.55

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:172 semgrep

Spreading entire process.env into an object — may capture all secrets 170 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 171 | > 172 | return { 173 | ...process.env, 174 | ...envFromDependencies

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.

v0.1.54

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:172 semgrep

Spreading entire process.env into an object — may capture all secrets 170 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 171 | > 172 | return { 173 | ...process.env, 174 | ...envFromDependencies

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.

v0.1.53

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:172 semgrep

Spreading entire process.env into an object — may capture all secrets 170 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 171 | > 172 | return { 173 | ...process.env, 174 | ...envFromDependencies

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.

v0.1.52

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:172 semgrep

Spreading entire process.env into an object — may capture all secrets 170 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 171 | > 172 | return { 173 | ...process.env, 174 | ...envFromDependencies

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.

v0.1.51

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:171 semgrep

Spreading entire process.env into an object — may capture all secrets 169 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 170 | > 171 | return { 172 | ...process.env, 173 | ...envFromDependencies

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.

v0.1.50

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:171 semgrep

Spreading entire process.env into an object — may capture all secrets 169 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 170 | > 171 | return { 172 | ...process.env, 173 | ...envFromDependencies

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.

v0.1.49

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:171 semgrep

Spreading entire process.env into an object — may capture all secrets 169 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 170 | > 171 | return { 172 | ...process.env, 173 | ...envFromDependencies

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.

v0.1.48

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:171 semgrep

Spreading entire process.env into an object — may capture all secrets 169 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 170 | > 171 | return { 172 | ...process.env, 173 | ...envFromDependencies

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.

v0.1.47

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:171 semgrep

Spreading entire process.env into an object — may capture all secrets 169 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 170 | > 171 | return { 172 | ...process.env, 173 | ...envFromDependencies

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.

v0.1.46

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:171 semgrep

Spreading entire process.env into an object — may capture all secrets 169 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; 170 | > 171 | return { 172 | ...process.env, 173 | ...envFromDependencies

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.

v0.1.45

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.44

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.43

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.42

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.41

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.40

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.39

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.38

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.37

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.36

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.35

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.34

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.33

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.32

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:169 semgrep

Spreading entire process.env into an object — may capture all secrets 167 | const envFromDependencies = 168 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 169 | const env = { 170 | ...process.env, 171 | ...envFromDependencies

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.

v0.1.31

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:165 semgrep

Spreading entire process.env into an object — may capture all secrets 163 | const envFromDependencies = 164 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 165 | const env = { 166 | ...process.env, 167 | ...envFromDependencies

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.

v0.1.30

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:165 semgrep

Spreading entire process.env into an object — may capture all secrets 163 | const envFromDependencies = 164 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 165 | const env = { 166 | ...process.env, 167 | ...envFromDependencies

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.

v0.1.29

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:165 semgrep

Spreading entire process.env into an object — may capture all secrets 163 | const envFromDependencies = 164 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 165 | const env = { 166 | ...process.env, 167 | ...envFromDependencies

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.

v0.1.28

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:165 semgrep

Spreading entire process.env into an object — may capture all secrets 163 | const envFromDependencies = 164 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 165 | const env = { 166 | ...process.env, 167 | ...envFromDependencies

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.

v0.1.27

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:165 semgrep

Spreading entire process.env into an object — may capture all secrets 163 | const envFromDependencies = 164 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 165 | const env = { 166 | ...process.env, 167 | ...envFromDependencies

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.

v0.1.25

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:165 semgrep

Spreading entire process.env into an object — may capture all secrets 163 | const envFromDependencies = 164 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 165 | const env = { 166 | ...process.env, 167 | ...envFromDependencies

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.

v0.1.24

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:165 semgrep

Spreading entire process.env into an object — may capture all secrets 163 | const envFromDependencies = 164 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 165 | const env = { 166 | ...process.env, 167 | ...envFromDependencies

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.

v0.1.23

2 findings
HIGH env-spread: src/server/providers/AuthSupabaseServiceProvider.js:165 semgrep

Spreading entire process.env into an object — may capture all secrets 163 | const envFromDependencies = 164 | dependencies?.env && typeof dependencies.env === "object" ? dependencies.env : {}; > 165 | const env = { 166 | ...process.env, 167 | ...envFromDependencies

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.

v0.1.22

1 finding
LOW No provenance attestation provenance

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

v0.1.21

1 finding
LOW No provenance attestation provenance

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

v0.1.20

1 finding
LOW No provenance attestation provenance

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

v0.1.19

1 finding
LOW No provenance attestation provenance

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

v0.1.18

1 finding
LOW No provenance attestation provenance

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

v0.1.17

1 finding
LOW No provenance attestation provenance

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

v0.1.16

1 finding
LOW No provenance attestation provenance

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

v0.1.15

1 finding
LOW No provenance attestation provenance

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

v0.1.14

1 finding
LOW No provenance attestation provenance

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

v0.1.13

1 finding
LOW No provenance attestation provenance

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

v0.1.12

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.5

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.

v0.1.4

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.