← Home

@peerbit/server

npm Repository Homepage
18
Versions
Apache-2.0
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

marcus.pousette

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:semver AI (typosquat): Scoped monorepo package @peerbit/server; Levenshtein match to 'semver' is a false positive. ai
semgrep semgrep:env-spread AI (semgrep): Server CLI spawning child processes; spreading process.env is standard and intentional here. ai
dependencies unvetted-dep:peerbit AI (dependencies): First-party peerbit monorepo dependency; stable false positive for this package. ai
dependencies unvetted-dep:@peerbit/time AI (dependencies): First-party @peerbit/* monorepo dependency. ai
dependencies unvetted-dep:@dao-xyz/borsh AI (dependencies): Same org (dao-xyz) serialization library; stable false positive. ai
dependencies unvetted-dep:@peerbit/blocks AI (dependencies): First-party @peerbit/* monorepo dependency. ai
dependencies unvetted-dep:@peerbit/crypto AI (dependencies): First-party @peerbit/* monorepo dependency. ai
dependencies unvetted-dep:@peerbit/pubsub AI (dependencies): First-party @peerbit/* monorepo dependency. ai
dependencies unvetted-dep:@peerbit/program AI (dependencies): First-party @peerbit/* monorepo dependency. ai
phantom-deps phantom-dep:@libp2p/tcp AI (phantom-deps): Referenced in config files for runtime use; stable false positive for this server package. ai
phantom-deps phantom-dep:@libp2p/websockets AI (phantom-deps): Referenced in config files for runtime use; stable false positive for this server package. ai

Versions (showing 18 of 18)

Version Deps Published
6.0.34 25 / 10
6.0.33 25 / 10
6.0.32 25 / 10
6.0.31 25 / 10
6.0.30 25 / 10
6.0.29 25 / 10
6.0.28 25 / 10
6.0.27 25 / 10
6.0.26 25 / 10
6.0.25 25 / 10
6.0.24 25 / 10
5.9.6 25 / 10
5.9.5 25 / 10
5.9.4 25 / 10
5.9.3 25 / 10
5.9.2 25 / 10
5.9.1 25 / 10
5.9.0 25 / 10

v6.0.34

1 finding
LOW No provenance attestation provenance

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

v6.0.33

1 finding
LOW No provenance attestation provenance

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

v6.0.32

1 finding
LOW No provenance attestation provenance

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

v6.0.31

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

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

HIGH env-spread: src/server.ts:361 semgrep

Spreading entire process.env into an object — may capture all secrets 359 | stdio: "inherit", 360 | gid: process.getgid!(), > 361 | env: { 362 | ...process.env, 363 | NODE_PATH:

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.

v6.0.30

1 finding
LOW No provenance attestation provenance

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

v6.0.29

1 finding
LOW No provenance attestation provenance

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

v6.0.28

1 finding
LOW No provenance attestation provenance

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

v6.0.27

1 finding
LOW No provenance attestation provenance

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

v6.0.26

1 finding
LOW No provenance attestation provenance

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

v6.0.25

1 finding
LOW No provenance attestation provenance

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

v5.9.6

1 finding
LOW No provenance attestation provenance

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

v5.9.5

1 finding
LOW No provenance attestation provenance

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

v5.9.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.

v5.9.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.

v5.9.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.

v5.9.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.

v5.9.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.