← Home

@reown/appkit-scaffold-ui

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

cyberdrkreown-npm-org

Keywords

appkitwalletonboardingreowndappsweb3wagmiethereumsolanabitcoin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transition to reown org account; official appkit publisher with clean track record. ai
maintainer-change maintainer-added AI (maintainer-change): reown-npm-org is the official org publisher; stable across versions. ai
maintainer-change maintainer-removed AI (maintainer-change): Individual devs replaced by org account in known transition. ai
dependencies unvetted-dep:@reown/appkit-utils AI (dependencies): First-party sibling package from the same reown-npm-org publisher, released in lockstep versioning. Not a security concern. ai
dependencies unvetted-dep:lit AI (dependencies): [email protected] is a well-known Google-maintained web components library; stable false positive for this UI package. ai
dependencies unvetted-dep:@reown/appkit-controllers AI (dependencies): First-party sibling package from the same reown-npm-org publisher, released in lockstep versioning. Not a security concern. ai
dependencies unvetted-dep:@reown/appkit-wallet AI (dependencies): First-party sibling package from the same reown-npm-org publisher, released in lockstep versioning. Not a security concern. ai
dependencies unvetted-dep:@reown/appkit-ui AI (dependencies): First-party sibling package from the same reown-npm-org publisher, released in lockstep versioning. Not a security concern. ai
dependencies unvetted-dep:@reown/appkit-pay AI (dependencies): First-party sibling package from the same reown-npm-org publisher, released in lockstep versioning. Not a security concern. ai

Versions (showing 82 of 82)

Version Deps Published
1.8.23 7 / 3
1.8.22 7 / 3
1.8.21 7 / 3
1.8.20 7 / 3
1.8.19 7 / 3
1.8.18 7 / 3
1.8.17 7 / 3
1.8.16 7 / 3
1.8.15 6 / 3
1.8.14 6 / 3
1.8.13 6 / 3
1.8.12 6 / 3
1.8.11 6 / 3
1.8.10 6 / 3
1.8.9 6 / 3
1.8.8 6 / 3
1.8.7 6 / 3
1.8.6 6 / 3
1.8.5 6 / 3
1.8.4 6 / 3
1.8.3 6 / 3
1.8.2 6 / 3
1.8.1 6 / 3
1.8.0 6 / 3
1.7.20 6 / 3
1.7.19 6 / 3
1.7.18 6 / 3
1.7.17 6 / 3
1.7.16 6 / 3
1.7.15 6 / 3
1.7.14 6 / 3
1.7.13 6 / 3
1.7.12 6 / 3
1.7.11 6 / 3
1.7.10 6 / 3
1.7.9 6 / 3
1.7.8 6 / 3
1.7.7 6 / 3
1.7.6 6 / 3
1.7.5 6 / 3
1.7.4 6 / 3
1.7.3 6 / 3
1.7.2 6 / 3
1.7.1 6 / 3
1.7.0 6 / 3
1.6.9 6 / 3
1.6.8 6 / 3
1.6.7 6 / 3
1.6.6 6 / 3
1.6.5 6 / 3
1.6.4 6 / 3
1.6.3 6 / 3
1.6.2 6 / 3
1.6.1 6 / 3
1.6.0 6 / 3
1.5.3 6 / 1
1.5.2 6 / 1
1.5.1 6 / 1
1.5.0 7 / 1
1.4.1 7 / 1
1.4.0 7 / 1
1.3.2 7 / 1
1.3.1 7 / 1
1.3.0 7 / 1
1.2.1 7 / 1
1.2.0 7 / 1
1.1.8 7 / 1
1.1.7 7 / 1
1.1.6 7 / 1
1.1.5 7 / 1
1.1.4 7 / 1
1.1.3 7 / 1
1.1.2 7 / 1
1.1.0 7 / 1
1.0.7 7 / 1
1.0.6 7 / 1
1.0.5 7 / 1
1.0.4 7 / 0
1.0.3 7 / 0
1.0.2 7 / 0
1.0.1 7 / 0
1.0.0 7 / 0

v1.8.23

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.

v1.8.22

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.

v1.7.3

2 findings
HIGH Publisher changed: rocky-wc → reown-npm-org (on 2025-04-15) provenance

This version was published by a different npm account than previous versions on 2025-04-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.7.2

1 finding
LOW No provenance attestation provenance

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

v1.7.1

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.9

1 finding
LOW No provenance attestation provenance

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

v1.6.8

1 finding
LOW No provenance attestation provenance

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

v1.6.7

1 finding
LOW No provenance attestation provenance

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

v1.6.6

1 finding
LOW No provenance attestation provenance

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

v1.6.5

1 finding
LOW No provenance attestation provenance

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

v1.6.4

1 finding
LOW No provenance attestation provenance

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

v1.6.3

1 finding
LOW No provenance attestation provenance

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

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.3

1 finding
LOW No provenance attestation provenance

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

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.8

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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