← Home

@datahousejs/server

10
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

eyueldk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:semver AI (typosquat): Scoped package @datahousejs/server; no intent to impersonate semver, completely different purpose and namespace. ai
phantom-deps phantom-dep:pg AI (phantom-deps): pg is a declared runtime dep used via config/drizzle integration; phantom-dep heuristic misfires here. ai
phantom-deps phantom-dep:bullmq AI (phantom-deps): bullmq is a declared runtime dep; phantom-dep heuristic misfires for this package. ai
phantom-deps phantom-dep:croner AI (phantom-deps): croner is a declared runtime dep; phantom-dep heuristic misfires for this package. ai

Versions (showing 10 of 10)

Version Deps Published
0.2.12 15 / 6
0.2.10 15 / 6
0.2.9 15 / 6
0.2.8 15 / 6
0.2.7 15 / 6
0.2.6 15 / 6
0.2.4 15 / 6
0.2.2 15 / 6
0.1.2 15 / 6
0.1.1 15 / 6

v0.2.12

1 finding
LOW No provenance attestation provenance

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

v0.2.10

1 finding
LOW No provenance attestation provenance

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

v0.2.9

1 finding
LOW No provenance attestation provenance

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

v0.2.8

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@datahousejs/server' is 1 edit(s) away from popular package 'semver'.

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.

v0.2.7

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@datahousejs/server' is 1 edit(s) away from popular package 'semver'.

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.

v0.2.6

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@datahousejs/server' is 1 edit(s) away from popular package 'semver'.

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.

v0.2.4

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@datahousejs/server' is 1 edit(s) away from popular package 'semver'.

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.

v0.2.2

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@datahousejs/server' is 1 edit(s) away from popular package 'semver'.

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.

v0.1.2

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@datahousejs/server' is 1 edit(s) away from popular package 'semver'.

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.

v0.1.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@datahousejs/server' is 1 edit(s) away from popular package 'semver'.

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.