@serve.zone/dcrouter
A multifaceted routing service handling mail and SMS delivery functions.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist_ts/email/classes.email-settings.manager.js | AI (source-diff): Readable TS-compiled JS; long lines from decorator emit, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist_ts_web/elements/network/ops-view-redirects.js | AI (source-diff): Standard TypeScript decorator boilerplate (__esDecorate/__runInitializers); not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/config/helpers.http-redirects.js | AI (source-diff): Readable TS-compiled JS utility functions; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist_ts/opsserver/handlers/email-settings.handler.js | AI (source-diff): Readable TS-compiled JS handler class; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist_ts/config/classes.source-policy-compiler.js | AI (source-diff): Readable TS-compiled JS with named exports and clear logic; not obfuscated. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartmigration | AI (phantom-deps): Newly added dep used in config/migration context, not directly imported; consistent with package's migration tooling pattern. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartdns | AI (dependencies): Same publisher ecosystem (@push.rocks); no independent malice signal. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartdb | AI (dependencies): Same publisher ecosystem (@push.rocks); no independent malice signal. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartmta | AI (dependencies): Same publisher ecosystem (@push.rocks); no independent malice signal. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartvpn | AI (dependencies): Same publisher ecosystem (@push.rocks); no independent malice signal. | ai | |
| dependencies | unvetted-dep:@serve.zone/remoteingress | AI (dependencies): Same publisher ecosystem (@serve.zone); no independent malice signal. | ai | |
| dependencies | unvetted-dep:@design.estate/dees-catalog | AI (dependencies): Related publisher ecosystem; no independent malice signal. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with long track record; lack of provenance is common for this ecosystem. | ai | |
| source-diff | obfuscated-file:dist_ts/email/classes.workapp-mail-manager.js | AI (source-diff): Readable compiled TS output; long lines from bundled/minified frontend code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/opsserver/handlers/workhoster.handler.js | AI (source-diff): Readable compiled TS handler code; long lines from bundled output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts_web/elements/access/ops-view-gatewayclients.js | AI (source-diff): Standard TypeScript decorator boilerplate; long lines are expected in bundled web output. | ai | |
| source-diff | obfuscated-file:dist_ts/config/classes.gateway-client-manager.js | AI (source-diff): Readable compiled TS output; long lines from bundled/minified frontend code, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@push.rocks/lik | AI (phantom-deps): Config-file reference pattern; stable false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@types/qrcode | AI (phantom-deps): Type-only package; not imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartstate | AI (phantom-deps): Config-file reference pattern; stable false positive for this ecosystem. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 14.2.0 | 42 / 8 | |
| 13.33.0 | 41 / 7 | |
| 13.25.0 | 40 / 6 | |
| 13.21.1 | 40 / 6 | |
| 13.17.0 | 40 / 6 | |
| 13.16.0 | 40 / 6 | |
| 13.9.2 | 40 / 6 | |
| 13.7.1 | 40 / 6 | |
| 13.4.2 | 40 / 6 | |
| 13.0.10 | 39 / 6 | |
| 13.0.7 | 39 / 6 | |
| 13.0.1 | 39 / 6 | |
| 12.9.3 | 39 / 6 | |
| 12.8.1 | 39 / 6 | |
| 12.6.5 | 39 / 6 | |
| 12.6.4 | 39 / 6 | |
| 12.6.2 | 39 / 6 | |
| 12.6.1 | 39 / 6 | |
| 12.5.2 | 39 / 6 | |
| 12.2.4 | 39 / 6 | |
| 11.23.5 | 39 / 6 | |
| 11.23.3 | 39 / 6 | |
| 11.23.2 | 39 / 6 | |
| 11.23.0 | 39 / 6 | |
| 11.22.0 | 39 / 6 | |
| 11.19.0 | 37 / 6 | |
| 11.15.0 | 37 / 6 | |
| 11.13.0 | 37 / 6 | |
| 5.0.2 | 32 / 6 |
v14.2.0
7 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.33.0
6 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.