@deessejs/server
Modern functional-first RPC protocol for type-safe APIs
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Scoped monorepo package; 0.0.0 reflects initial bootstrap, not throwaway malware pattern. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped package @deessejs/server; 'server' vs 'semver' similarity is coincidental, not an impersonation attempt. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 0 / 12 | |
| 1.2.0 | 0 / 12 | |
| 1.1.2 | 0 / 12 | |
| 1.0.1 | 0 / 12 | |
| 0.0.0 | 0 / 8 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.