← Home

@ariakit/react

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

diegohazariakit-botbenrodrsdaniguardiola

Keywords

a11yariakitcomponentsreacttoolkitui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:cjs/__chunks/JBOLBTVU.cjs AI (source-diff): Standard CJS bundler output (esbuild helpers), not obfuscation. Stable for this package. ai
source-diff large-new-source-files AI (source-diff): Component library regularly reshuffles CJS chunks across versions. ai
source-diff obfuscated-file:cjs/__chunks/QAUJZR6Y.cjs AI (source-diff): Standard CJS bundler output (esbuild helpers), not obfuscation; stable for this package. ai
provenance missing-githead AI (provenance): CI environment change; SLSA provenance present, established package with strong ecosystem trust. ai
publish-pattern dormant-publish AI (publish-pattern): Long-lived popular package; dormancy is normal for stable UI libraries. ai
dependencies unvetted-dep:@ariakit/react-core AI (dependencies): Internal monorepo sibling package; stable false positive for this package family. ai

Versions (showing 12 of 12)

Version Deps Published
0.4.29 1 / 2
0.4.28 1 / 2
0.4.27 1 / 2
0.4.26 1 / 2
0.4.25 1 / 2
0.4.24 1 / 2
0.4.23 1 / 0
0.4.22 1 / 0
0.4.21 1 / 0
0.4.20 1 / 0
0.4.19 1 / 0
0.4.18 1 / 0

v0.4.29

2 findings
HIGH New obfuscated file: cjs/__chunks/JBOLBTVU.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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

3 findings
HIGH New obfuscated file: cjs/__chunks/QAUJZR6Y.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v0.4.27

3 findings
HIGH New obfuscated file: cjs/__chunks/QAUJZR6Y.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v0.4.26

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.

v0.4.25

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.

v0.4.24

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

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

v0.4.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.

v0.4.21

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.

v0.4.20

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.

v0.4.19

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.

v0.4.18

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.