@terreno/ui
[](https://app.netlify.com/sites/terreno-ui/deploys)
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-datetime-picker | AI (phantom-deps): UI library pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-app-polyfill | AI (phantom-deps): Referenced in babel/browserslist config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-time-picker | AI (phantom-deps): Same as above; platform-specific UI dep pattern. | ai | |
| phantom-deps | phantom-dep:react-date-picker | AI (phantom-deps): UI library with platform-specific deps; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:@react-native-community/blur | AI (phantom-deps): Platform-specific native binary dep; phantom-dep heuristic not applicable. | ai | |
| phantom-deps | phantom-dep:react-native-webview | AI (phantom-deps): Platform-specific native dep; expected for RN UI library. | ai | |
| phantom-deps | phantom-dep:react-dev-utils | AI (phantom-deps): Config-referenced dev dep; expected pattern. | ai | |
| phantom-deps | phantom-dep:expo-font | AI (phantom-deps): Platform/config-referenced dep; expected pattern for Expo UI library. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Web platform dep; expected for cross-platform RN library. | ai | |
| phantom-deps | phantom-dep:expo-linking | AI (phantom-deps): Config-referenced Expo dep; expected pattern. | ai | |
| phantom-deps | phantom-dep:expo-updates | AI (phantom-deps): Config-referenced Expo dep; expected pattern. | ai | |
| phantom-deps | phantom-dep:expo-web-browser | AI (phantom-deps): Config-referenced Expo dep; expected pattern. | ai | |
| phantom-deps | phantom-dep:react-native-web | AI (phantom-deps): Platform-specific binary dep; expected for RN web support. | ai | |
| phantom-deps | phantom-dep:react-native-screens | AI (phantom-deps): Platform-specific native dep; expected for RN navigation. | ai | |
| phantom-deps | phantom-dep:react-native-safe-area-context | AI (phantom-deps): Platform-specific native dep; expected for RN UI library. | ai | |
| phantom-deps | phantom-dep:expo-router | AI (phantom-deps): Config-referenced Expo dep; expected pattern. | ai | |
| phantom-deps | phantom-dep:expo-notifications | AI (phantom-deps): Config-referenced Expo dep; expected pattern. | ai | |
| phantom-deps | phantom-dep:expo-splash-screen | AI (phantom-deps): Config-referenced Expo dep; expected pattern. | ai | |
| phantom-deps | phantom-dep:react-native-picker-select | AI (phantom-deps): Platform-specific native dep; expected for RN UI library. | ai | |
| phantom-deps | phantom-dep:react-native-worklets | AI (phantom-deps): Platform-specific native dep; expected for RN reanimated. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; no resemblance to uuid in purpose or namespace. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; no resemblance to yup in purpose or namespace. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; no resemblance to joi in purpose or namespace. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; no resemblance to qs in purpose or namespace. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; no resemblance to pg in purpose or namespace. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.17.0 | 56 / 23 | |
| 0.16.1 | 56 / 23 | |
| 0.16.0 | 56 / 23 | |
| 0.15.2 | 56 / 23 | |
| 0.15.1 | 56 / 23 | |
| 0.15.0 | 56 / 23 | |
| 0.11.6 | 56 / 24 | |
| 0.9.0 | 56 / 24 | |
| 0.0.17 | 54 / 22 | |
| 0.0.16 | 54 / 22 | |
| 0.0.14 | 54 / 22 | |
| 0.0.12 | 45 / 22 | |
| 0.0.1 | 45 / 22 |
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.