← Home

@vertz/server

npm Repository
4
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

viniciusdacal

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:semver AI (typosquat): @vertz/server is a scoped monorepo package (server runtime), not a typosquat of semver; name similarity is coincidental. ai
dependencies unvetted-dep:@vertz/db AI (dependencies): Internal monorepo sibling dependency; stable false positive for this package. ai
dependencies unvetted-dep:@vertz/core AI (dependencies): Internal monorepo sibling dependency; stable false positive for this package. ai

Versions (showing 4 of 4)

Version Deps Published
0.2.56 6 / 0
0.2.54 6 / 0
0.2.1 5 / 5
0.2.0 3 / 6

v0.2.56

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.

v0.2.54

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.

v0.2.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.

v0.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.