@bison-lab/ui
React components, form system, and blocks for Bison Lab component library
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance attestation is a best-practice recommendation, not a blocker for this package. | ai | |
| dependencies | unvetted-dep:@fortawesome/pro-regular-svg-icons | AI (dependencies): Legitimate Font Awesome Pro scoped package; no malware indicators, stable icon library. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped org package @bison-lab/ui; Levenshtein match to qs is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped org package @bison-lab/ui; Levenshtein match to joi is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped org package @bison-lab/ui; Levenshtein match to yup is a false positive. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped org package @bison-lab/ui; Levenshtein match to uuid is a false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-image | AI (phantom-deps): TipTap extension declared as dep for consumers; config-only reference is expected pattern. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-code-block-lowlight | AI (phantom-deps): TipTap extension declared as dep for consumers; config-only reference is expected pattern. | ai | |
| phantom-deps | phantom-dep:@tiptap/pm | AI (phantom-deps): TipTap peer/transitive dep; referenced in config but not directly imported is expected for this UI library. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped org package @bison-lab/ui; Levenshtein match to pg is a false positive. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 22 / 12 | |
| 1.0.2 | 22 / 12 | |
| 1.0.1 | 22 / 12 | |
| 1.0.0 | 22 / 12 | |
| 0.21.0 | 24 / 12 | |
| 0.20.0 | 24 / 12 | |
| 0.18.1 | 24 / 12 | |
| 0.18.0 | 24 / 12 | |
| 0.16.1 | 24 / 12 | |
| 0.16.0 | 24 / 12 | |
| 0.14.1 | 23 / 7 | |
| 0.14.0 | 23 / 7 | |
| 0.13.2 | 21 / 7 | |
| 0.13.0 | 21 / 7 | |
| 0.12.1 | 10 / 7 | |
| 0.12.0 | 10 / 7 | |
| 0.11.0 | 10 / 7 | |
| 0.10.1 | 10 / 7 | |
| 0.10.0 | 10 / 7 | |
| 0.9.0 | 10 / 7 | |
| 0.8.0 | 10 / 7 | |
| 0.7.0 | 9 / 7 | |
| 0.6.0 | 9 / 6 | |
| 0.5.0 | 9 / 6 | |
| 0.4.0 | 9 / 6 | |
| 0.3.1 | 9 / 6 | |
| 0.3.0 | 9 / 6 | |
| 0.2.0 | 9 / 6 | |
| 0.1.0 | 9 / 6 |
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.