@contractspec/lib.example-shared-ui
**Shared React components and hooks for ContractSpec example apps. Provides the common layout, editors, and overlays used across all examples.**
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is normal for internal libs. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic fires on config-only refs but deps are present. | ai | |
| phantom-deps | phantom-dep:framer-motion | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic fires on config-only refs but deps are present. | ai | |
| dependencies | unvetted-dep:@contractspec/lib.design-system | AI (dependencies): Internal @contractspec scoped dependency; consistent with the package's own ecosystem across versions. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 7.0.10 | 6 / 9 | |
| 7.0.9 | 6 / 9 | |
| 7.0.8 | 6 / 9 | |
| 7.0.7 | 6 / 9 | |
| 7.0.6 | 6 / 9 | |
| 7.0.5 | 6 / 9 | |
| 7.0.4 | 6 / 9 | |
| 7.0.3 | 6 / 9 | |
| 7.0.2 | 6 / 9 | |
| 7.0.1 | 6 / 9 | |
| 7.0.0 | 6 / 9 | |
| 6.0.22 | 10 / 5 | |
| 6.0.20 | 10 / 5 | |
| 6.0.19 | 10 / 5 | |
| 6.0.18 | 10 / 5 | |
| 6.0.17 | 10 / 5 | |
| 6.0.16 | 10 / 5 | |
| 6.0.15 | 10 / 5 | |
| 6.0.14 | 10 / 5 | |
| 6.0.12 | 10 / 5 | |
| 6.0.10 | 9 / 5 | |
| 6.0.7 | 9 / 5 | |
| 6.0.6 | 9 / 6 | |
| 6.0.5 | 9 / 6 | |
| 6.0.4 | 9 / 6 | |
| 6.0.1 | 9 / 6 | |
| 6.0.0 | 9 / 6 | |
| 5.0.0 | 9 / 6 | |
| 4.0.5 | 9 / 6 | |
| 4.0.4 | 9 / 6 | |
| 4.0.3 | 9 / 6 | |
| 4.0.2 | 9 / 6 | |
| 4.0.0 | 9 / 6 | |
| 3.4.3 | 9 / 6 | |
| 3.4.2 | 9 / 6 | |
| 3.4.1 | 9 / 6 | |
| 3.4.0 | 9 / 6 | |
| 3.3.0 | 9 / 6 | |
| 3.2.0 | 9 / 6 | |
| 3.1.1 | 9 / 6 | |
| 3.0.0 | 9 / 6 | |
| 2.9.1 | 9 / 6 | |
| 2.9.0 | 9 / 6 | |
| 2.8.0 | 9 / 6 | |
| 2.7.0 | 9 / 6 | |
| 2.6.1 | 9 / 6 | |
| 2.6.0 | 9 / 6 | |
| 2.5.0 | 9 / 6 | |
| 2.4.0 | 9 / 6 | |
| 2.3.0 | 9 / 6 | |
| 2.2.0 | 9 / 6 | |
| 2.1.1 | 9 / 6 | |
| 2.1.0 | 9 / 6 | |
| 2.0.0 | 9 / 6 | |
| 1.16.0 | 9 / 6 | |
| 1.15.0 | 9 / 6 | |
| 1.14.0 | 9 / 6 | |
| 1.13.0 | 9 / 6 | |
| 1.12.0 | 9 / 6 | |
| 1.11.0 | 9 / 5 | |
| 1.10.1 | 9 / 5 | |
| 1.10.0 | 9 / 5 | |
| 1.9.0 | 9 / 5 | |
| 1.8.0 | 9 / 5 | |
| 1.7.0 | 9 / 5 | |
| 1.6.0 | 9 / 5 | |
| 1.5.0 | 9 / 5 | |
| 1.4.0 | 9 / 5 | |
| 1.3.0 | 9 / 5 | |
| 1.2.1 | 9 / 5 | |
| 1.2.0 | 9 / 5 | |
| 1.1.0 | 9 / 5 |
v7.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.