@ditojs/server
Dito.js Server – Dito.js is a declarative and modern web framework, based on Objection.js, Koa.js and Vue.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:multer-s3 | AI (dependencies): Points to ditojs org's own fork; intentional custom fork pattern for this package. | ai | |
| npm-metadata | url-dep:multer-s3 | AI (npm-metadata): GitHub URL dep is the package's own org fork; stable pattern for this project. | ai | |
| phantom-deps | phantom-dep:@ditojs/admin | AI (phantom-deps): Same-org package; likely used indirectly via re-export or build tooling, stable false positive. | ai | |
| phantom-deps | phantom-dep:multer | AI (phantom-deps): Referenced in config/type context; @koa/multer wraps multer, making direct import unnecessary. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped @ditojs/server is a long-established web framework; Levenshtein match to 'semver' is a false positive. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding used for crypto.timingSafeEqual HMAC comparison — not obfuscation or payload hiding. | ai |
Versions (showing 89 of 89)
| Version | Deps | Published |
|---|---|---|
| 2.99.1 | 43 / 13 | |
| 2.99.0 | 43 / 13 | |
| 2.98.0 | 43 / 13 | |
| 2.97.0 | 43 / 13 | |
| 2.96.0 | 43 / 13 | |
| 2.95.0 | 43 / 13 | |
| 2.94.1 | 43 / 13 | |
| 2.92.0 | 43 / 13 | |
| 2.91.0 | 43 / 13 | |
| 2.90.0 | 43 / 13 | |
| 2.89.0 | 43 / 13 | |
| 2.88.0 | 43 / 13 | |
| 2.87.0 | 43 / 13 | |
| 2.86.0 | 43 / 12 | |
| 2.85.2 | 43 / 12 | |
| 2.85.1 | 43 / 12 | |
| 2.85.0 | 43 / 12 | |
| 2.84.1 | 43 / 12 | |
| 2.84.0 | 43 / 12 | |
| 2.83.0 | 43 / 12 | |
| 2.82.0 | 43 / 12 | |
| 2.81.0 | 43 / 12 | |
| 2.80.0 | 43 / 12 | |
| 2.79.0 | 43 / 12 | |
| 2.78.0 | 43 / 12 | |
| 2.77.1 | 43 / 12 | |
| 2.77.0 | 43 / 12 | |
| 2.75.2 | 43 / 12 | |
| 2.75.1 | 43 / 12 | |
| 2.75.0 | 43 / 12 | |
| 2.74.0 | 43 / 12 | |
| 2.73.4 | 43 / 12 | |
| 2.73.3 | 43 / 12 | |
| 2.73.2 | 43 / 12 | |
| 2.73.1 | 43 / 12 | |
| 2.73.0 | 43 / 12 | |
| 2.72.0 | 43 / 12 | |
| 2.71.1 | 43 / 12 | |
| 2.71.0 | 43 / 12 | |
| 2.70.0 | 43 / 12 | |
| 2.69.0 | 43 / 12 | |
| 2.68.0 | 43 / 12 | |
| 2.67.0 | 43 / 12 | |
| 2.66.0 | 43 / 12 | |
| 2.65.0 | 43 / 12 | |
| 2.64.0 | 43 / 12 | |
| 2.63.0 | 43 / 12 | |
| 2.62.0 | 43 / 12 | |
| 2.61.0 | 43 / 12 | |
| 2.60.0 | 43 / 12 | |
| 2.59.0 | 43 / 12 | |
| 2.58.2 | 43 / 12 | |
| 2.58.1 | 43 / 12 | |
| 2.58.0 | 43 / 12 | |
| 2.57.0 | 43 / 12 | |
| 2.56.0 | 43 / 12 | |
| 2.55.0 | 43 / 12 | |
| 2.54.0 | 43 / 12 | |
| 2.53.1 | 43 / 12 | |
| 2.53.0 | 43 / 12 | |
| 2.52.0 | 43 / 12 | |
| 2.51.2 | 43 / 12 | |
| 2.51.1 | 43 / 12 | |
| 2.51.0 | 43 / 12 | |
| 2.50.0 | 44 / 12 | |
| 2.49.1 | 43 / 12 | |
| 2.49.0 | 43 / 12 | |
| 2.48.0 | 43 / 12 | |
| 2.47.0 | 43 / 12 | |
| 2.46.1 | 43 / 12 | |
| 2.46.0 | 43 / 12 | |
| 2.45.1 | 43 / 12 | |
| 2.45.0 | 43 / 12 | |
| 2.44.0 | 43 / 12 | |
| 2.43.1 | 43 / 12 | |
| 2.43.0 | 43 / 12 | |
| 2.42.2 | 43 / 12 | |
| 2.42.1 | 43 / 12 | |
| 2.42.0 | 43 / 12 | |
| 2.41.0 | 43 / 12 | |
| 2.40.0 | 43 / 12 | |
| 2.39.0 | 43 / 12 | |
| 2.38.0 | 43 / 12 | |
| 2.37.1 | 43 / 12 | |
| 2.37.0 | 43 / 12 | |
| 2.36.2 | 42 / 12 | |
| 2.36.1 | 42 / 12 | |
| 2.36.0 | 42 / 12 | |
| 2.35.0 | 42 / 12 |
v2.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.