@ditojs/server MIT 51 versions

@ditojs/server

npm Repository Homepage

Dito.js Server – Dito.js is a declarative and modern web framework, based on Objection.js, Koa.js and Vue.js

51

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

lehnibotrunner

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	2026/05/17
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	2026/05/17
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	2026/05/17
phantom-deps	phantom-dep:multer	AI (phantom-deps): Referenced in config/type context; @koa/multer wraps multer, making direct import unnecessary.	ai	2026/05/17
typosquat	typosquat.levenshtein:semver	AI (typosquat): Scoped @ditojs/server is a long-established web framework; Levenshtein match to 'semver' is a false positive.	ai	2026/04/29
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding used for crypto.timingSafeEqual HMAC comparison — not obfuscation or payload hiding.	ai	2026/04/29

Versions (showing 51 of 70)

View all versions

Version	Deps	Published
2.99.1	43 / 13	2026-05-19
2.99.0	43 / 13	2026-05-19
2.98.0	43 / 13	2026-04-29
2.97.0	43 / 13	2026-04-29
2.96.0	43 / 13	2026-04-27
2.95.0	43 / 13	2026-04-16
2.94.1	43 / 13	2026-04-14
2.92.0	43 / 13	2026-03-18
2.91.0	43 / 13	2026-03-12
2.90.0	43 / 13	2026-03-12
2.89.0	43 / 13	2026-03-12
2.88.0	43 / 13	2026-03-12
2.87.0	43 / 13	2026-03-12
2.86.0	43 / 12	2026-03-12
2.85.2	43 / 12	2026-03-09
2.85.1	43 / 12	2026-03-09
2.85.0	43 / 12	2026-03-09
2.84.1	43 / 12	2026-02-26
2.84.0	43 / 12	2026-02-26
2.83.0	43 / 12	2026-02-23
2.82.0	43 / 12	2026-02-10
2.81.0	43 / 12	2026-02-04
2.80.0	43 / 12	2026-01-30
2.79.0	43 / 12	2026-01-29
2.78.0	43 / 12	2026-01-27
2.77.1	43 / 12	2026-01-16
2.77.0	43 / 12	2026-01-16
2.75.2	43 / 12	2026-01-15
2.75.1	43 / 12	2026-01-12
2.75.0	43 / 12	2026-01-12
2.74.0	43 / 12	2026-01-12
2.73.4	43 / 12	2026-01-09
2.73.3	43 / 12	2026-01-09
2.73.2	43 / 12	2026-01-09
2.73.1	43 / 12	2026-01-08
2.73.0	43 / 12	2026-01-08
2.72.0	43 / 12	2026-01-08
2.71.1	43 / 12	2025-12-30
2.71.0	43 / 12	2025-12-30
2.70.0	43 / 12	2025-12-23
2.69.0	43 / 12	2025-12-22
2.68.0	43 / 12	2025-12-07
2.67.0	43 / 12	2025-12-07
2.66.0	43 / 12	2025-12-07
2.65.0	43 / 12	2025-11-29
2.64.0	43 / 12	2025-11-27
2.63.0	43 / 12	2025-11-22
2.62.0	43 / 12	2025-11-08
2.61.0	43 / 12	2025-10-14
2.60.0	43 / 12	2025-09-08
2.59.0	43 / 12	2025-09-03

v2.99.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.99.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.98.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.96.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.95.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.94.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.92.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.91.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.90.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.89.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.88.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.87.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.86.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.85.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.85.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.85.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.84.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.84.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.83.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.82.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.81.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.80.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.79.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.78.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.77.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.77.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.75.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.75.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.75.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.74.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.73.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.73.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.73.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.73.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.73.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.72.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.71.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.71.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.70.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.69.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.68.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.67.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.66.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.65.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.64.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.63.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.62.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.61.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.60.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.59.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.