@simplysm/core-common
심플리즘 패키지 - 코어 (common)
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 config pattern in a config module; not malicious, stable across versions. | ai |
Versions (showing 81 of 185)
| Version | Deps | Published |
|---|---|---|
| 13.0.95 | 4 / 0 | |
| 13.0.93 | 4 / 0 | |
| 13.0.92 | 4 / 0 | |
| 13.0.91 | 4 / 0 | |
| 13.0.90 | 4 / 0 | |
| 13.0.89 | 4 / 0 | |
| 13.0.88 | 4 / 0 | |
| 13.0.87 | 4 / 0 | |
| 13.0.86 | 4 / 0 | |
| 13.0.85 | 4 / 0 | |
| 13.0.84 | 4 / 0 | |
| 13.0.83 | 4 / 0 | |
| 13.0.82 | 4 / 0 | |
| 13.0.81 | 4 / 0 | |
| 13.0.80 | 4 / 0 | |
| 13.0.78 | 4 / 0 | |
| 13.0.77 | 4 / 0 | |
| 13.0.76 | 4 / 0 | |
| 13.0.75 | 4 / 0 | |
| 13.0.74 | 4 / 0 | |
| 13.0.72 | 4 / 0 | |
| 13.0.71 | 4 / 0 | |
| 13.0.70 | 4 / 0 | |
| 13.0.69 | 4 / 0 | |
| 13.0.68 | 4 / 0 | |
| 13.0.67 | 4 / 0 | |
| 13.0.66 | 4 / 0 | |
| 13.0.65 | 4 / 0 | |
| 13.0.64 | 4 / 0 | |
| 13.0.62 | 4 / 0 | |
| 13.0.61 | 4 / 0 | |
| 13.0.60 | 4 / 0 | |
| 13.0.59 | 4 / 0 | |
| 13.0.58 | 4 / 0 | |
| 13.0.57 | 4 / 0 | |
| 13.0.56 | 4 / 0 | |
| 13.0.55 | 4 / 0 | |
| 13.0.53 | 4 / 0 | |
| 13.0.51 | 4 / 0 | |
| 13.0.50 | 4 / 0 | |
| 13.0.49 | 4 / 0 | |
| 13.0.48 | 4 / 0 | |
| 13.0.47 | 4 / 0 | |
| 13.0.45 | 4 / 0 | |
| 13.0.44 | 4 / 0 | |
| 13.0.43 | 4 / 0 | |
| 13.0.42 | 4 / 0 | |
| 13.0.41 | 4 / 0 | |
| 13.0.40 | 4 / 0 | |
| 13.0.39 | 4 / 0 | |
| 13.0.38 | 4 / 0 | |
| 13.0.37 | 4 / 0 | |
| 13.0.36 | 4 / 0 | |
| 13.0.35 | 4 / 0 | |
| 13.0.34 | 4 / 0 | |
| 13.0.33 | 4 / 0 | |
| 13.0.32 | 4 / 0 | |
| 13.0.31 | 4 / 0 | |
| 13.0.30 | 4 / 0 | |
| 13.0.29 | 4 / 0 | |
| 13.0.28 | 4 / 0 | |
| 13.0.27 | 4 / 0 | |
| 13.0.26 | 4 / 0 | |
| 13.0.25 | 4 / 0 | |
| 13.0.24 | 4 / 0 | |
| 13.0.23 | 4 / 0 | |
| 13.0.22 | 4 / 0 | |
| 13.0.20 | 4 / 0 | |
| 13.0.18 | 4 / 0 | |
| 13.0.16 | 4 / 0 | |
| 13.0.15 | 4 / 0 | |
| 13.0.14 | 4 / 0 | |
| 13.0.13 | 4 / 0 | |
| 13.0.12 | 4 / 0 | |
| 13.0.11 | 4 / 0 | |
| 13.0.10 | 4 / 0 | |
| 13.0.8 | 4 / 0 | |
| 13.0.7 | 4 / 0 | |
| 13.0.3 | 4 / 0 | |
| 13.0.2 | 4 / 0 | |
| 13.0.1 | 4 / 0 |
v13.0.95
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.93
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.92
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.91
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.90
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.89
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.88
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.87
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.86
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.85
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.84
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.83
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.82
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.81
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.80
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.78
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.77
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.76
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.75
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.74
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.72
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.71
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.70
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.69
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.68
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.67
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.66
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.65
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.64
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.62
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.61
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.60
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.59
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.58
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.57
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.56
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.55
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.53
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.51
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.50
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.49
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.48
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.47
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.45
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.44
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.43
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.42
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.41
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.40
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.39
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.38
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.37
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.36
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.35
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.34
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.33
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.32
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.31
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.30
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.29
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.28
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.27
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.26
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.25
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.24
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.23
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.22
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.20
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.18
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.16
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.15
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.14
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.13
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.12
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.11
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.10
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.8
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.7
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.3
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.2
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.1
2 findingsSpreading entire process.env into an object — may capture all secrets 5 | VER?: string; 6 | [key: string]: unknown; > 7 | } = { 8 | ...process.env, 9 | DEV: JSON.parse(process.env.DEV != null && process.env.DEV !== "" ? process.env.DEV : "false"),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.