← Home

@rein-ai/server

npm Repository Homepage
10
Versions
—
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

havasik

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:semver AI (typosquat): Scoped @rein-ai package; name collision with semver is incidental, not impersonation. ai

Versions (showing 10 of 10)

Version Deps Published
1.0.0 2 / 1
0.7.0 2 / 1
0.6.1 2 / 1
0.5.0 3 / 2
0.4.1 3 / 2
0.4.0 3 / 2
0.3.0 2 / 1
0.2.0 2 / 1
0.1.1 2 / 1
0.1.0 2 / 1

v1.0.0

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

Package name '@rein-ai/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.7.0

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

Package name '@rein-ai/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.6.1

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

Package name '@rein-ai/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.5.0

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

Package name '@rein-ai/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.4.1

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

Package name '@rein-ai/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.4.0

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

Package name '@rein-ai/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.3.0

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

Package name '@rein-ai/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.0

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

Package name '@rein-ai/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 '@rein-ai/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.0

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

Package name '@rein-ai/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.