← Home

@reference-ui/rust

npm Repository Homepage

Reference UI Rust and native bindings

34
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

peacelove

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Bundled .node binaries are expected napi-rs artifacts for platform-specific native bindings; SLSA provenance attestation confirms CI/CD provenance. Stable pattern for this package. ai
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped package @reference-ui/rust is not impersonating nuxt; Levenshtein match is superficial and not a credible typosquat. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped package @reference-ui/rust is not impersonating jest; Levenshtein match is superficial and not a credible typosquat. ai

Versions (showing 34 of 34)

Version Deps Published
0.0.40 0 / 5
0.0.39 0 / 5
0.0.38 0 / 5
0.0.37 0 / 5
0.0.36 0 / 5
0.0.35 0 / 5
0.0.34 0 / 5
0.0.33 0 / 5
0.0.32 0 / 5
0.0.31 0 / 5
0.0.30 0 / 5
0.0.29 0 / 5
0.0.28 0 / 5
0.0.27 0 / 5
0.0.26 0 / 5
0.0.25 0 / 5
0.0.24 0 / 5
0.0.23 0 / 5
0.0.22 0 / 5
0.0.21 0 / 5
0.0.16 0 / 5
0.0.15 0 / 5
0.0.14 0 / 5
0.0.12 0 / 5
0.0.11 0 / 5
0.0.10 0 / 5
0.0.9 0 / 5
0.0.7 0 / 5
0.0.6 0 / 5
0.0.5 0 / 5
0.0.4 0 / 5
0.0.3 0 / 4
0.0.2 0 / 4
0.0.1 0 / 4

v0.0.40

1 finding
LOW No provenance attestation provenance

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

v0.0.39

1 finding
LOW No provenance attestation provenance

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

v0.0.38

1 finding
LOW No provenance attestation provenance

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

v0.0.37

1 finding
LOW No provenance attestation provenance

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

v0.0.36

1 finding
LOW No provenance attestation provenance

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

v0.0.35

1 finding
LOW No provenance attestation provenance

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

v0.0.34

1 finding
LOW No provenance attestation provenance

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

v0.0.33

1 finding
LOW No provenance attestation provenance

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

v0.0.32

1 finding
LOW No provenance attestation provenance

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

v0.0.31

1 finding
LOW No provenance attestation provenance

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

v0.0.30

1 finding
LOW No provenance attestation provenance

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

v0.0.29

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • native/virtual-native.darwin-x64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • native/virtual-native.darwin-x64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • native/virtual-native.darwin-x64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • native/virtual-native.darwin-x64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • native/virtual-native.darwin-x64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • native/virtual-native.darwin-x64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • native/virtual-native.darwin-x64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • native/virtual-native.darwin-x64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • native/virtual-native.darwin-x64.node

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

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.15

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.14

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • native/virtual-native.linux-x64-gnu.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.12

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • native/virtual-native.linux-x64-gnu.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.11

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.10

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.9

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.7

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.6

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.5

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.4

2 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node

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.

v0.0.3

2 findings
HIGH Bundled binary files (8) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node • virtual-native.win32-x64-msvc.node

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.

v0.0.2

2 findings
HIGH Bundled binary files (8) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node • virtual-native.win32-x64-msvc.node

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.

v0.0.1

2 findings
HIGH Bundled binary files (8) npm-metadata

Package contains compiled binaries that could be backdoors: • npm/darwin-arm64/virtual-native.darwin-arm64.node • virtual-native.darwin-arm64.node • npm/darwin-x64/virtual-native.darwin-x64.node • virtual-native.darwin-x64.node • npm/linux-x64-gnu/virtual-native.linux-x64-gnu.node • virtual-native.linux-x64-gnu.node • npm/win32-x64-msvc/virtual-native.win32-x64-msvc.node • virtual-native.win32-x64-msvc.node

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.