@wise/art
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @wise/art is a React UI library; no relation to 'got'. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @wise/art is a React UI library; no relation to 'ajv'. Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:@types/three | AI (phantom-deps): @types/three is a type-only dep used at compile time; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is injected by Babel transforms at build time; not directly imported in source. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.30.2 | 7 / 46 | |
| 2.30.1 | 7 / 46 | |
| 2.30.0 | 7 / 46 | |
| 2.29.0 | 7 / 46 | |
| 2.28.0 | 7 / 46 | |
| 2.27.2 | 7 / 47 | |
| 2.27.1 | 7 / 47 | |
| 2.27.0 | 7 / 47 | |
| 2.26.0 | 7 / 47 | |
| 2.25.3 | 7 / 47 | |
| 2.25.2 | 7 / 47 | |
| 2.25.0 | 7 / 47 | |
| 2.23.0 | 6 / 46 |
v2.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
2 findingsDependency 'wise-atoms' in `devDependencies` points to 'git+https://github.com/transferwise/wise-atoms.git#a88088f08aee11d4d3b09ab541706db1d2490d0e' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.