@headlessui/react
A set of completely unstyled, fully accessible UI components for React, designed to integrate beautifully with Tailwind CSS.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/internal/floating.js | AI (source-diff): This is a minified build artifact bundling @floating-ui/react logic. Standard build output for headlessui; not obfuscation. Stable for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version (v2.0.0) of a component library; large number of new files is expected for a significant feature release. | ai | |
| source-diff | obfuscated-file:dist/components/combobox/combobox-machine.js | AI (source-diff): Minified dist output is expected for @headlessui/react; these are standard build artifacts, not obfuscated malware. Pattern is stable across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/components/listbox/listbox-machine.js | AI (source-diff): Minified dist output is expected for @headlessui/react; these are standard build artifacts, not obfuscated malware. Pattern is stable across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/components/menu/menu-machine.js | AI (source-diff): Minified dist output is expected for @headlessui/react; these are standard build artifacts, not obfuscated malware. Pattern is stable across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@react-aria/focus | AI (phantom-deps): Package is listed in dependencies in package.json; phantom-dep finding is a false positive from indirect import detection in this build setup. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-virtual | AI (phantom-deps): Package is listed in dependencies in package.json; phantom-dep finding is a false positive from indirect import detection in this build setup. | ai | |
| phantom-deps | phantom-dep:@react-aria/interactions | AI (phantom-deps): Package is listed in dependencies in package.json; phantom-dep finding is a false positive from indirect import detection in this build setup. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 2.2.10 | 5 / 8 | |
| 2.2.9 | 5 / 8 | |
| 2.2.8 | 5 / 8 | |
| 2.2.7 | 5 / 8 | |
| 2.2.6 | 5 / 8 | |
| 2.2.5 | 5 / 8 | |
| 2.2.4 | 5 / 8 | |
| 2.2.3 | 5 / 8 | |
| 2.2.2 | 5 / 8 | |
| 2.2.1 | 4 / 7 | |
| 2.2.0 | 4 / 7 | |
| 2.1.10 | 4 / 7 | |
| 2.1.9 | 4 / 7 | |
| 2.1.8 | 4 / 7 | |
| 2.1.7 | 4 / 7 | |
| 2.1.6 | 4 / 6 | |
| 2.1.5 | 4 / 6 | |
| 2.1.4 | 4 / 6 | |
| 2.1.3 | 4 / 6 | |
| 2.1.2 | 4 / 6 | |
| 2.1.1 | 4 / 6 | |
| 2.1.0 | 4 / 6 | |
| 2.0.4 | 4 / 6 | |
| 2.0.3 | 4 / 6 | |
| 2.0.2 | 4 / 6 | |
| 2.0.1 | 4 / 6 | |
| 2.0.0 | 4 / 6 | |
| 1.7.19 | 2 / 7 | |
| 1.7.18 | 2 / 7 | |
| 1.7.16 | 1 / 7 | |
| 1.7.15 | 1 / 7 | |
| 1.7.14 | 1 / 7 | |
| 1.7.13 | 1 / 7 | |
| 1.7.12 | 1 / 7 | |
| 1.7.11 | 1 / 7 | |
| 1.7.10 | 1 / 7 | |
| 1.7.9 | 1 / 7 | |
| 1.7.8 | 1 / 7 | |
| 1.7.7 | 1 / 7 | |
| 1.7.6 | 1 / 7 | |
| 1.7.5 | 1 / 7 | |
| 1.7.4 | 1 / 7 | |
| 1.7.3 | 0 / 7 | |
| 1.7.2 | 0 / 7 | |
| 1.7.1 | 0 / 7 | |
| 1.7.0 | 0 / 7 | |
| 1.6.6 | 0 / 7 | |
| 1.6.5 | 0 / 7 | |
| 1.6.4 | 0 / 7 | |
| 1.6.3 | 0 / 7 | |
| 1.6.2 | 0 / 7 |
v2.2.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.