← Home

@stacks/transactions

npm Repository Homepage
6
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Hiro Systems org consolidation; blockstack-devops is a known org publisher with approved track record. ai
publish-pattern dormant-publish AI (publish-pattern): Major version release from established Hiro/Stacks org; dormancy consistent with v6→v7 development cycle. ai
source-diff large-new-source-files AI (source-diff): 105 new files consistent with major version bump; no suspicious deps or install scripts added. ai
dependencies unvetted-dep:@stacks/common AI (dependencies): @stacks/common is a sibling package in the same Hiro Systems stacks.js monorepo; always a legitimate dependency for this package. ai
dependencies unvetted-dep:@stacks/network AI (dependencies): @stacks/network is a sibling package in the same Hiro Systems stacks.js monorepo; always a legitimate dependency for this package. ai

Versions (showing 6 of 6)

Version Deps Published
7.4.0 6 / 8
7.3.1 6 / 8
7.3.0 6 / 8
7.2.0 6 / 8
7.1.0 6 / 8
6.17.0 6 / 8

v7.4.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.

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.3.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.

v7.2.0

1 finding
LOW No provenance attestation provenance

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

v7.1.0

1 finding
LOW No provenance attestation provenance

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.