@tre-regex/regex-darwin-arm64
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
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI, consistent with automated publishing; SLSA attestation confirms CI provenance. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific native .node binary is the entire purpose of this package; SLSA provenance confirms CI/CD build. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform binary shards have no deps and minimal READMEs by design; not spam. | ai |
v0.3.1
2 findingsPackage contains compiled binaries that could be backdoors: • tre-regex.darwin-arm64.node
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 findingsPackage contains compiled binaries that could be backdoors: • tre-regex.darwin-arm64.node
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
3 findingsPackage contains compiled binaries that could be backdoors: • tre-regex.darwin-arm64.node
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.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.