← Home

@radix-ui/react-arrow

This is an internal utility, not intended for public usage.

20
Versions
MIT
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

hadihallakchancestricklandmark-workosnpm-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Radix UI moved to GitHub Actions CI/CD publishing with SLSA provenance; legitimate transition. ai
provenance missing-githead AI (provenance): GitHub Actions publish flow omits gitHead; compensated by SLSA provenance attestation. ai
maintainer-change maintainer-added AI (maintainer-change): npm-workos reflects WorkOS acquisition of Radix UI; legitimate org change. ai
maintainer-change maintainer-removed AI (maintainer-change): Previous individual maintainers replaced by org account after WorkOS acquisition. ai
bogus-package bogus-package AI (bogus-package): Radix UI sub-package; minimal README and no keywords are normal for scoped monorepo components. ai

Versions (showing 20 of 20)

Version Deps Published
1.1.15 1 / 7
1.1.14 1 / 7
1.1.13 1 / 7
1.1.12 1 / 7
1.1.11 1 / 7
1.1.10 1 / 7
1.1.9 1 / 7
1.1.8 1 / 9
1.1.7 1 / 9
1.1.6 1 / 9
1.1.5 1 / 9
1.1.4 1 / 9
1.1.3 1 / 8
1.1.2 1 / 8
1.1.1 1 / 0
1.1.0 1 / 0
1.0.3 2 / 0
1.0.2 2 / 0
1.0.1 2 / 0
1.0.0 2 / 0

v1.1.15

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

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

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

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

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

2 findings
LOW No provenance attestation provenance

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

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: chancestrickland.

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

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.

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

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.