@simplysm/excel
심플리즘 패키지 - 엑셀 (neutral)
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
Versions (showing 51 of 174)
| Version | Deps | Published |
|---|---|---|
| 14.0.94 | 3 / 1 | |
| 14.0.93 | 3 / 1 | |
| 14.0.92 | 3 / 1 | |
| 14.0.91 | 3 / 1 | |
| 14.0.90 | 3 / 1 | |
| 14.0.89 | 3 / 1 | |
| 14.0.88 | 3 / 1 | |
| 14.0.87 | 3 / 1 | |
| 14.0.86 | 3 / 1 | |
| 14.0.85 | 3 / 1 | |
| 14.0.84 | 3 / 1 | |
| 14.0.83 | 3 / 1 | |
| 14.0.82 | 3 / 1 | |
| 14.0.81 | 3 / 1 | |
| 14.0.80 | 3 / 1 | |
| 14.0.79 | 3 / 1 | |
| 14.0.78 | 3 / 1 | |
| 14.0.77 | 3 / 1 | |
| 14.0.76 | 3 / 1 | |
| 14.0.75 | 3 / 1 | |
| 14.0.74 | 3 / 1 | |
| 14.0.73 | 3 / 1 | |
| 14.0.72 | 3 / 1 | |
| 14.0.71 | 3 / 1 | |
| 14.0.70 | 3 / 1 | |
| 14.0.69 | 3 / 1 | |
| 14.0.66 | 3 / 1 | |
| 14.0.65 | 3 / 1 | |
| 14.0.64 | 3 / 1 | |
| 14.0.63 | 3 / 1 | |
| 14.0.62 | 3 / 1 | |
| 14.0.61 | 3 / 1 | |
| 14.0.60 | 3 / 1 | |
| 14.0.59 | 3 / 1 | |
| 14.0.58 | 3 / 1 | |
| 14.0.57 | 3 / 1 | |
| 14.0.56 | 3 / 1 | |
| 14.0.55 | 3 / 1 | |
| 14.0.54 | 3 / 1 | |
| 14.0.53 | 3 / 1 | |
| 14.0.52 | 3 / 1 | |
| 14.0.51 | 3 / 1 | |
| 14.0.50 | 3 / 1 | |
| 14.0.49 | 3 / 1 | |
| 14.0.48 | 3 / 1 | |
| 14.0.47 | 3 / 1 | |
| 14.0.46 | 3 / 1 | |
| 14.0.45 | 3 / 1 | |
| 14.0.44 | 3 / 1 | |
| 14.0.43 | 3 / 1 | |
| 14.0.42 | 3 / 1 |
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.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.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.