@faststore/ui
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 package @faststore/ui; Levenshtein match to uuid is a false positive for this established library. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @faststore/ui; Levenshtein match to pg is a false positive for this established library. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @faststore/ui; Levenshtein match to qs is a false positive for this established library. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @faststore/ui; Levenshtein match to joi is a false positive for this established library. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @faststore/ui; Levenshtein match to yup is a false positive for this established library. | ai | |
| phantom-deps | phantom-dep:tabbable | AI (phantom-deps): UI library; tabbable used via config/types, not direct JS import — stable false positive. | ai | |
| phantom-deps | phantom-dep:include-media | AI (phantom-deps): CSS/SCSS utility dep; not directly imported in JS — stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:react-swipeable | AI (phantom-deps): UI component dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:modern-normalize | AI (phantom-deps): CSS normalization dep; not directly imported in JS — stable false positive for this UI library. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 5 / 10 | |
| 4.1.0 | 5 / 10 | |
| 4.0.0 | 5 / 10 | |
| 3.99.4 | 5 / 7 | |
| 3.99.2 | 5 / 7 | |
| 3.99.1 | 5 / 7 | |
| 3.99.0 | 5 / 7 | |
| 3.98.1 | 5 / 7 | |
| 3.98.0 | 5 / 7 | |
| 3.97.1 | 5 / 7 | |
| 3.97.0 | 5 / 7 | |
| 3.96.0 | 5 / 7 | |
| 3.95.0 | 5 / 7 | |
| 3.94.0 | 5 / 7 | |
| 3.93.0 | 5 / 7 | |
| 3.92.0 | 5 / 7 | |
| 3.91.2 | 5 / 7 | |
| 3.89.2 | 5 / 7 | |
| 3.89.0 | 5 / 7 | |
| 3.88.0 | 5 / 7 | |
| 3.87.0 | 5 / 7 | |
| 3.86.4 | 5 / 7 | |
| 3.84.0 | 5 / 7 | |
| 3.81.0 | 5 / 7 | |
| 3.80.0 | 5 / 7 | |
| 3.78.0 | 5 / 7 | |
| 3.70.2 | 5 / 7 | |
| 3.68.0 | 5 / 7 | |
| 3.65.0 | 5 / 7 | |
| 3.60.4 | 5 / 7 | |
| 3.56.1 | 5 / 7 | |
| 3.50.3 | 5 / 7 | |
| 3.49.1 | 5 / 7 | |
| 3.47.1 | 5 / 7 | |
| 3.45.0 | 5 / 7 | |
| 3.44.0 | 5 / 7 | |
| 3.42.0 | 5 / 7 |
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.99.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.99.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.99.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.99.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.98.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.98.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.97.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.97.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.96.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.91.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.86.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.70.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.60.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.50.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.