← Home

@tre-regex/regex-linux-arm-gnueabihf

npm Repository Homepage

TreRegex provides a high-performance Node interface to the TRE C library. It brings robust approximate (fuzzy) regular expression matching to Node, featuring multi-byte Unicode string safety, and granular error limits

4
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

leopard_me

Keywords

fuzzy-regexregextrefuzzy-regular-expressions

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI is a legitimate automation migration, consistent with SLSA provenance attestation. ai
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific native binding package; .node binary is the intended deliverable, published with SLSA provenance. ai
bogus-package bogus-package AI (bogus-package): Platform-split package; no deps and sparse README are expected for this pattern. ai

Versions (showing 4 of 4)

Version Deps Published
0.3.1 0 / 0
0.3.0 0 / 0
0.2.1 0 / 0
0.2.0 0 / 0

v0.3.1

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

Package contains compiled binaries that could be backdoors: • tre-regex.linux-arm-gnueabihf.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.3.0

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

Package contains compiled binaries that could be backdoors: • tre-regex.linux-arm-gnueabihf.node

HIGH Publisher changed: leopard_me → GitHub Actions (on 2026-05-02) provenance

This version was published by a different npm account than previous versions on 2026-05-02. This could indicate a legitimate maintainer transition or an account compromise.

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

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

Package contains compiled binaries that could be backdoors: • tre-regex.linux-arm-gnueabihf.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.2.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.