← Home

@xstate/store

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

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

davidkpianoandarist

Keywords

storestate

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from xstate-release-bot to GitHub Actions is consistent with SLSA-attested CI/CD publishing; not a compromise signal. ai

Versions (showing 47 of 47)

Version Deps Published
4.2.1 0 / 11
4.2.0 0 / 11
4.1.0 0 / 11
4.0.0 0 / 11
3.17.5 0 / 16
3.17.4 0 / 16
3.17.3 0 / 16
3.17.2 0 / 16
3.17.1 0 / 16
3.17.0 0 / 16
3.16.0 0 / 16
3.15.0 0 / 16
3.14.1 0 / 16
3.14.0 0 / 16
3.13.0 0 / 16
3.12.0 0 / 16
3.11.2 0 / 16
3.11.1 0 / 16
3.11.0 0 / 16
3.10.0 0 / 16
3.9.3 0 / 16
3.9.2 0 / 16
3.9.1 0 / 16
3.9.0 0 / 16
3.8.5 0 / 16
3.8.4 0 / 16
3.8.3 0 / 16
3.8.2 0 / 16
3.8.1 0 / 16
3.8.0 0 / 16
3.7.1 0 / 16
3.7.0 0 / 16
3.6.2 0 / 12
3.6.1 0 / 12
3.6.0 0 / 12
3.5.1 0 / 12
3.5.0 0 / 12
3.4.3 0 / 12
3.4.2 0 / 12
3.4.1 0 / 12
3.4.0 0 / 12
3.3.0 0 / 12
3.2.1 0 / 12
3.2.0 0 / 12
3.1.0 0 / 12
3.0.1 0 / 12
3.0.0 0 / 12

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

v3.5.1

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.3

1 finding
LOW No provenance attestation provenance

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

v3.4.2

1 finding
LOW No provenance attestation provenance

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

v3.4.1

1 finding
LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.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.