← Home

@stacks/network

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ablanksteinblockstack-devopsstacks-foundationjannik-stacks

Keywords

blockstacknetworkstacks

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@stacks/common AI (dependencies): @stacks/common is a sibling package in the same @stacks monorepo published by Hiro Systems PBC; not an independent risk. ai
phantom-deps phantom-dep:cross-fetch AI (phantom-deps): cross-fetch is a legitimate, well-known fetch polyfill declared as a runtime dep; phantom finding reflects indirect usage pattern, not a real risk. ai
provenance no-provenance AI (provenance): Established Hiro Systems package from a known monorepo; lack of Sigstore provenance is common and not a risk signal here. ai

Versions (showing 3 of 3)

Version Deps Published
7.3.1 2 / 2
7.2.0 2 / 2
6.17.0 2 / 2

v7.3.1

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.

v7.2.0

1 finding
INFO No provenance attestation provenance

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

v6.17.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.