@sil/ui
Shared UI components for SIL applications
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI component library; name collision is coincidental, not a squatting attempt. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI component library; name collision is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI component library; name collision is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI component library; name collision is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI component library; name collision is coincidental. | ai | |
| phantom-deps | phantom-dep:lowlight | AI (phantom-deps): Referenced in config/build files for tiptap code-block extension; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sil/color | AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for scoped sibling packages. | ai | |
| phantom-deps | phantom-dep:@tiptap/pm | AI (phantom-deps): Tiptap peer/config reference; stable false positive for this Vue UI library. | ai | |
| phantom-deps | phantom-dep:@tiptap/vue-3 | AI (phantom-deps): Tiptap peer/config reference; stable false positive for this Vue UI library. | ai | |
| phantom-deps | phantom-dep:@tiptap/starter-kit | AI (phantom-deps): Tiptap peer/config reference; stable false positive for this Vue UI library. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-link | AI (phantom-deps): Tiptap peer/config reference; stable false positive for this Vue UI library. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-image | AI (phantom-deps): Tiptap peer/config reference; stable false positive for this Vue UI library. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-underline | AI (phantom-deps): Tiptap peer/config reference; stable false positive for this Vue UI library. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-placeholder | AI (phantom-deps): Tiptap peer/config reference; stable false positive for this Vue UI library. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-code-block-lowlight | AI (phantom-deps): Tiptap peer/config reference; stable false positive for this Vue UI library. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.6.0 | 12 / 26 | |
| 2.5.0 | 12 / 26 | |
| 2.4.0 | 12 / 26 | |
| 2.3.5 | 12 / 26 | |
| 2.3.4 | 12 / 26 | |
| 2.3.2 | 12 / 26 | |
| 2.3.1 | 12 / 26 | |
| 2.3.0 | 12 / 26 | |
| 2.2.0 | 12 / 26 | |
| 2.1.0 | 12 / 26 | |
| 2.0.1 | 12 / 26 | |
| 2.0.0 | 12 / 26 | |
| 1.27.0 | 12 / 26 | |
| 1.26.0 | 12 / 26 | |
| 1.25.1 | 12 / 26 | |
| 1.25.0 | 12 / 26 | |
| 1.24.2 | 12 / 26 | |
| 1.14.0 | 11 / 28 | |
| 1.0.2 | 1 / 25 |
v2.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
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.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
2 findingsMaintainer email '[email protected]' uses domain 'silvandiepen.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
2 findingsMaintainer email '[email protected]' uses domain 'silvandiepen.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.