@contractspec/lib.design-system
Design tokens and theming primitives
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/browser/components/data-view/collection.js | AI (source-diff): Standard minified build output with readable named exports; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/browser/components/shell/ShellNotifications.js | AI (source-diff): Standard minified build output with readable JSX transpilation; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/components/data-view/collection.js | AI (source-diff): Standard minified build output with readable named exports; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/browser/components/shell/AppShell.js | AI (source-diff): Minified browser bundle output; readable React/JSX logic with named imports from known packages — not obfuscation. | ai | |
| phantom-deps | phantom-dep:country-flag-icons | AI (phantom-deps): UI component dep; referenced in config, stable false positive. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): Form validation dep; referenced in config, stable false positive. | ai | |
| phantom-deps | phantom-dep:next | AI (phantom-deps): Design system with Next.js support; declared as peer/optional dep, not directly imported. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.ui-kit-core | AI (phantom-deps): Same-org package; declared dep used via config, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:react-native-safe-area-context | AI (phantom-deps): Platform-specific binary; expected for cross-platform design system. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): CSS animation plugin; referenced in config, stable false positive. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Web platform dep for cross-platform UI library; referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Tailwind utility used via config; stable false positive for this design system. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Form library dep referenced in config; expected for a design system with form controls. | ai |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 4.4.4 | 27 / 11 | |
| 4.4.3 | 27 / 11 | |
| 4.4.2 | 27 / 11 | |
| 4.4.1 | 27 / 11 | |
| 4.4.0 | 27 / 11 | |
| 4.3.0 | 18 / 10 | |
| 4.2.0 | 18 / 10 | |
| 4.1.0 | 18 / 10 | |
| 4.0.0 | 18 / 10 | |
| 3.11.2 | 18 / 10 | |
| 3.11.1 | 18 / 10 | |
| 3.11.0 | 18 / 10 | |
| 3.10.0 | 18 / 10 | |
| 3.9.0 | 18 / 10 | |
| 3.8.11 | 18 / 10 | |
| 3.8.10 | 18 / 10 | |
| 3.8.9 | 18 / 10 | |
| 3.8.8 | 18 / 10 | |
| 3.8.7 | 18 / 10 | |
| 3.8.5 | 18 / 10 | |
| 3.8.3 | 18 / 10 | |
| 3.8.0 | 18 / 10 | |
| 3.7.6 | 17 / 10 | |
| 3.7.5 | 17 / 10 | |
| 3.7.4 | 17 / 10 | |
| 3.7.3 | 17 / 10 | |
| 3.7.1 | 17 / 10 | |
| 3.7.0 | 17 / 10 | |
| 3.6.0 | 17 / 10 | |
| 3.5.5 | 17 / 10 | |
| 3.5.4 | 17 / 10 | |
| 3.5.3 | 17 / 10 | |
| 3.5.2 | 17 / 10 | |
| 3.5.0 | 17 / 10 | |
| 3.4.3 | 17 / 10 | |
| 3.4.2 | 17 / 10 | |
| 3.4.1 | 17 / 10 | |
| 3.4.0 | 17 / 10 | |
| 3.3.0 | 17 / 10 | |
| 3.2.0 | 17 / 10 | |
| 3.1.1 | 17 / 10 | |
| 3.0.0 | 17 / 10 | |
| 2.9.1 | 17 / 10 | |
| 2.9.0 | 17 / 10 | |
| 2.8.0 | 17 / 10 | |
| 2.7.0 | 17 / 10 | |
| 2.6.1 | 17 / 10 | |
| 2.6.0 | 17 / 10 | |
| 2.5.0 | 17 / 10 | |
| 2.4.0 | 17 / 10 | |
| 2.3.0 | 17 / 10 | |
| 2.2.0 | 17 / 10 | |
| 2.1.1 | 17 / 10 | |
| 2.1.0 | 17 / 10 | |
| 2.0.0 | 17 / 10 | |
| 1.62.0 | 16 / 10 | |
| 1.61.0 | 16 / 10 | |
| 1.60.0 | 16 / 10 | |
| 1.59.0 | 16 / 10 | |
| 1.58.0 | 16 / 10 | |
| 1.57.0 | 16 / 11 | |
| 1.56.1 | 16 / 11 | |
| 1.56.0 | 16 / 11 | |
| 1.55.0 | 16 / 11 | |
| 1.54.0 | 16 / 11 | |
| 1.53.0 | 16 / 11 | |
| 1.52.0 | 16 / 11 | |
| 1.51.0 | 16 / 11 | |
| 1.50.0 | 16 / 11 | |
| 1.49.0 | 16 / 11 | |
| 1.48.1 | 16 / 11 | |
| 1.48.0 | 16 / 11 | |
| 1.47.0 | 16 / 11 | |
| 1.46.2 | 14 / 8 | |
| 1.46.1 | 14 / 8 | |
| 1.46.0 | 14 / 8 | |
| 1.45.6 | 14 / 8 | |
| 1.45.5 | 14 / 8 | |
| 1.45.4 | 14 / 8 | |
| 1.45.3 | 14 / 8 | |
| 1.45.2 | 14 / 8 | |
| 1.45.1 | 14 / 8 | |
| 1.45.0 | 14 / 8 | |
| 1.44.1 | 14 / 8 | |
| 1.44.0 | 14 / 8 |
v4.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.