@typemove/move
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:mobx | AI (typosquat): Scoped package in the typemove ecosystem; edit-distance match to mobx is coincidental, not a typosquat. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.13.4 | 1 / 0 | |
| 1.13.3 | 1 / 0 | |
| 1.13.2 | 1 / 0 | |
| 1.13.1 | 1 / 0 | |
| 1.13.0 | 1 / 0 | |
| 1.12.0 | 1 / 0 | |
| 1.11.0 | 1 / 0 | |
| 1.10.0 | 1 / 0 |
v1.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.