@simplysm/service-server
심플리즘 패키지 - 서비스 (server)
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mime | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:nodemailer | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/middie | AI (phantom-deps): Fastify plugin used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/reply-from | AI (phantom-deps): Fastify plugin used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:bufferutil | AI (phantom-deps): bufferutil is an optional native binding for ws; declared but not directly imported is expected behavior. | ai | |
| phantom-deps | phantom-dep:utf-8-validate | AI (phantom-deps): utf-8-validate is an optional native binding for ws; declared but not directly imported is expected behavior. | ai |
Versions (showing 100 of 168)
| Version | Deps | Published |
|---|---|---|
| 14.0.95 | 16 / 2 | |
| 14.0.94 | 16 / 2 | |
| 14.0.93 | 16 / 2 | |
| 14.0.92 | 16 / 2 | |
| 14.0.91 | 16 / 2 | |
| 14.0.90 | 16 / 2 | |
| 14.0.89 | 16 / 2 | |
| 14.0.88 | 16 / 2 | |
| 14.0.87 | 16 / 2 | |
| 14.0.86 | 16 / 2 | |
| 14.0.85 | 16 / 2 | |
| 14.0.84 | 16 / 2 | |
| 14.0.83 | 16 / 2 | |
| 14.0.82 | 16 / 2 | |
| 14.0.81 | 16 / 2 | |
| 14.0.80 | 16 / 2 | |
| 14.0.79 | 16 / 2 | |
| 14.0.78 | 16 / 2 | |
| 14.0.76 | 17 / 2 | |
| 14.0.75 | 17 / 2 | |
| 14.0.74 | 17 / 2 | |
| 14.0.73 | 17 / 2 | |
| 14.0.72 | 17 / 2 | |
| 14.0.71 | 17 / 2 | |
| 14.0.70 | 17 / 2 | |
| 14.0.69 | 17 / 2 | |
| 14.0.66 | 17 / 2 | |
| 14.0.65 | 17 / 2 | |
| 14.0.64 | 17 / 2 | |
| 14.0.63 | 17 / 2 | |
| 14.0.62 | 17 / 2 | |
| 14.0.61 | 17 / 2 | |
| 14.0.60 | 17 / 2 | |
| 14.0.59 | 17 / 2 | |
| 14.0.58 | 17 / 2 | |
| 14.0.57 | 17 / 2 | |
| 14.0.56 | 17 / 2 | |
| 14.0.55 | 17 / 2 | |
| 14.0.54 | 17 / 2 | |
| 14.0.53 | 17 / 2 | |
| 14.0.52 | 17 / 2 | |
| 14.0.51 | 17 / 2 | |
| 14.0.49 | 17 / 2 | |
| 14.0.48 | 17 / 2 | |
| 14.0.47 | 17 / 2 | |
| 14.0.46 | 17 / 2 | |
| 14.0.45 | 17 / 2 | |
| 14.0.44 | 17 / 2 | |
| 14.0.43 | 17 / 2 | |
| 14.0.42 | 17 / 2 | |
| 14.0.41 | 17 / 2 | |
| 14.0.40 | 17 / 2 | |
| 14.0.39 | 17 / 2 | |
| 14.0.38 | 17 / 2 | |
| 14.0.37 | 17 / 2 | |
| 14.0.36 | 17 / 2 | |
| 14.0.35 | 17 / 2 | |
| 14.0.33 | 17 / 2 | |
| 14.0.32 | 17 / 2 | |
| 14.0.30 | 17 / 2 | |
| 14.0.29 | 17 / 2 | |
| 14.0.28 | 17 / 2 | |
| 14.0.27 | 17 / 2 | |
| 14.0.26 | 17 / 2 | |
| 14.0.25 | 17 / 2 | |
| 14.0.24 | 17 / 2 | |
| 14.0.23 | 17 / 2 | |
| 14.0.22 | 17 / 2 | |
| 14.0.21 | 17 / 2 | |
| 14.0.19 | 17 / 2 | |
| 14.0.18 | 17 / 2 | |
| 14.0.17 | 17 / 2 | |
| 14.0.16 | 17 / 2 | |
| 14.0.15 | 17 / 2 | |
| 14.0.14 | 17 / 2 | |
| 14.0.13 | 17 / 2 | |
| 14.0.12 | 17 / 2 | |
| 14.0.11 | 17 / 2 | |
| 14.0.10 | 17 / 2 | |
| 14.0.9 | 17 / 2 | |
| 14.0.8 | 17 / 2 | |
| 14.0.7 | 17 / 2 | |
| 14.0.6 | 21 / 3 | |
| 14.0.5 | 21 / 3 | |
| 14.0.4 | 21 / 3 | |
| 14.0.1 | 21 / 3 | |
| 13.0.100 | 21 / 3 | |
| 13.0.99 | 21 / 3 | |
| 13.0.98 | 21 / 3 | |
| 13.0.97 | 21 / 3 | |
| 13.0.96 | 21 / 3 | |
| 13.0.95 | 21 / 3 | |
| 13.0.93 | 21 / 3 | |
| 13.0.92 | 21 / 3 | |
| 13.0.91 | 21 / 3 | |
| 13.0.90 | 21 / 3 | |
| 13.0.89 | 21 / 3 | |
| 13.0.88 | 21 / 3 | |
| 13.0.86 | 21 / 3 | |
| 13.0.85 | 21 / 3 |
v14.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.