@thi.ng/morton
Z-order curve / Morton encoding, decoding & range extraction for arbitrary dimensions
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:morgan | AI (typosquat): @thi.ng/morton is a legitimate Z-order curve library in the thi.ng/umbrella monorepo, not a typosquat of morgan. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.1.149 | 4 / 3 | |
| 3.1.148 | 4 / 3 | |
| 3.1.147 | 4 / 3 | |
| 3.1.145 | 4 / 3 | |
| 3.1.144 | 4 / 3 | |
| 3.1.143 | 4 / 3 | |
| 3.1.142 | 4 / 3 | |
| 3.1.141 | 4 / 3 | |
| 3.1.140 | 4 / 3 | |
| 3.1.139 | 4 / 3 | |
| 3.1.138 | 4 / 3 | |
| 3.1.137 | 4 / 3 | |
| 3.1.136 | 4 / 3 | |
| 3.1.135 | 4 / 3 | |
| 3.1.134 | 4 / 3 | |
| 3.1.133 | 4 / 3 | |
| 3.1.132 | 4 / 3 | |
| 3.1.131 | 4 / 3 | |
| 3.1.130 | 4 / 3 | |
| 3.1.129 | 4 / 3 | |
| 3.1.128 | 4 / 3 | |
| 3.1.124 | 4 / 3 | |
| 3.1.123 | 4 / 3 | |
| 3.1.122 | 4 / 3 | |
| 3.1.121 | 4 / 3 | |
| 3.1.120 | 4 / 3 | |
| 3.1.119 | 4 / 3 | |
| 3.1.118 | 4 / 3 | |
| 3.1.117 | 4 / 3 | |
| 3.1.116 | 4 / 3 | |
| 3.1.115 | 4 / 3 | |
| 3.1.114 | 4 / 3 |
v3.1.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.