@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 100 of 177)
| Version | Deps | Published |
|---|---|---|
| 14.0.94 | 4 / 1 | |
| 14.0.93 | 4 / 1 | |
| 14.0.92 | 4 / 1 | |
| 14.0.91 | 4 / 1 | |
| 14.0.90 | 4 / 1 | |
| 14.0.89 | 4 / 1 | |
| 14.0.88 | 4 / 1 | |
| 14.0.87 | 4 / 1 | |
| 14.0.86 | 4 / 1 | |
| 14.0.85 | 4 / 1 | |
| 14.0.84 | 4 / 1 | |
| 14.0.83 | 4 / 1 | |
| 14.0.82 | 4 / 1 | |
| 14.0.81 | 4 / 1 | |
| 14.0.80 | 4 / 1 | |
| 14.0.79 | 4 / 1 | |
| 14.0.78 | 4 / 1 | |
| 14.0.77 | 4 / 1 | |
| 14.0.76 | 4 / 1 | |
| 14.0.75 | 4 / 1 | |
| 14.0.74 | 4 / 1 | |
| 14.0.73 | 4 / 1 | |
| 14.0.72 | 4 / 1 | |
| 14.0.71 | 4 / 1 | |
| 14.0.70 | 4 / 1 | |
| 14.0.69 | 4 / 1 | |
| 14.0.68 | 4 / 1 | |
| 14.0.67 | 4 / 1 | |
| 14.0.66 | 4 / 1 | |
| 14.0.65 | 4 / 1 | |
| 14.0.64 | 4 / 1 | |
| 14.0.63 | 4 / 1 | |
| 14.0.62 | 4 / 1 | |
| 14.0.61 | 4 / 1 | |
| 14.0.60 | 4 / 1 | |
| 14.0.59 | 4 / 1 | |
| 14.0.58 | 4 / 1 | |
| 14.0.57 | 4 / 1 | |
| 14.0.56 | 4 / 1 | |
| 14.0.55 | 4 / 1 | |
| 14.0.54 | 4 / 1 | |
| 14.0.53 | 4 / 1 | |
| 14.0.52 | 4 / 1 | |
| 14.0.51 | 4 / 1 | |
| 14.0.50 | 4 / 1 | |
| 14.0.49 | 4 / 1 | |
| 14.0.48 | 4 / 1 | |
| 14.0.47 | 4 / 1 | |
| 14.0.46 | 4 / 1 | |
| 14.0.45 | 4 / 1 | |
| 14.0.44 | 4 / 1 | |
| 14.0.43 | 4 / 1 | |
| 14.0.42 | 4 / 1 | |
| 14.0.41 | 4 / 1 | |
| 14.0.40 | 4 / 1 | |
| 14.0.39 | 4 / 1 | |
| 14.0.38 | 4 / 1 | |
| 14.0.37 | 4 / 1 | |
| 14.0.36 | 4 / 1 | |
| 14.0.35 | 4 / 1 | |
| 14.0.33 | 4 / 1 | |
| 14.0.32 | 4 / 1 | |
| 14.0.31 | 4 / 1 | |
| 14.0.30 | 4 / 1 | |
| 14.0.29 | 4 / 1 | |
| 14.0.28 | 4 / 1 | |
| 14.0.27 | 4 / 1 | |
| 14.0.26 | 4 / 1 | |
| 14.0.25 | 4 / 1 | |
| 14.0.24 | 4 / 1 | |
| 14.0.23 | 4 / 1 | |
| 14.0.22 | 4 / 1 | |
| 14.0.21 | 4 / 1 | |
| 14.0.20 | 4 / 1 | |
| 14.0.19 | 4 / 1 | |
| 14.0.18 | 4 / 1 | |
| 14.0.17 | 4 / 1 | |
| 14.0.16 | 4 / 1 | |
| 14.0.15 | 4 / 1 | |
| 14.0.14 | 4 / 1 | |
| 14.0.13 | 4 / 1 | |
| 14.0.12 | 4 / 1 | |
| 14.0.11 | 4 / 1 | |
| 14.0.10 | 4 / 1 | |
| 14.0.9 | 4 / 1 | |
| 14.0.8 | 4 / 1 | |
| 14.0.7 | 4 / 1 | |
| 14.0.6 | 4 / 1 | |
| 14.0.5 | 4 / 1 | |
| 14.0.4 | 4 / 1 | |
| 14.0.1 | 4 / 0 | |
| 13.0.100 | 4 / 0 | |
| 13.0.99 | 4 / 0 | |
| 13.0.98 | 4 / 0 | |
| 13.0.97 | 4 / 0 | |
| 13.0.96 | 4 / 0 | |
| 13.0.95 | 4 / 0 | |
| 13.0.93 | 4 / 0 | |
| 13.0.92 | 4 / 0 | |
| 13.0.91 | 4 / 0 |
v14.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.96
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.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.