@thi.ng/axidraw
Minimal AxiDraw plotter/drawing machine controller for Node.js
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Same thi.ng/umbrella monorepo; stable sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/date | AI (dependencies): Same thi.ng/umbrella monorepo; stable sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/math | AI (dependencies): Same thi.ng/umbrella monorepo; stable sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/units | AI (dependencies): Same thi.ng/umbrella monorepo; stable sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/compose | AI (dependencies): Same thi.ng/umbrella monorepo; stable sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Same thi.ng/umbrella monorepo; stable sibling dep. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Same thi.ng/umbrella monorepo; stable sibling dep. | ai | |
| provenance | no-provenance | AI (provenance): thi.ng/umbrella does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.1.190 | 11 / 3 | |
| 1.1.189 | 11 / 3 | |
| 1.1.188 | 11 / 3 | |
| 1.1.186 | 11 / 3 | |
| 1.1.185 | 11 / 3 | |
| 1.1.184 | 11 / 3 | |
| 1.1.183 | 11 / 3 | |
| 1.1.181 | 11 / 3 | |
| 1.1.180 | 11 / 3 | |
| 1.1.179 | 11 / 3 | |
| 1.1.178 | 11 / 3 | |
| 1.1.177 | 11 / 3 | |
| 1.1.176 | 11 / 3 | |
| 1.1.175 | 11 / 3 | |
| 1.1.174 | 11 / 3 | |
| 1.1.173 | 11 / 3 | |
| 1.1.172 | 11 / 3 | |
| 1.1.171 | 11 / 3 | |
| 1.1.170 | 11 / 3 | |
| 1.1.169 | 11 / 3 | |
| 1.1.167 | 11 / 3 | |
| 1.1.166 | 11 / 3 | |
| 1.1.165 | 11 / 3 | |
| 1.1.164 | 11 / 3 | |
| 1.1.163 | 11 / 3 | |
| 1.1.162 | 11 / 3 | |
| 1.1.161 | 11 / 3 | |
| 1.1.160 | 11 / 3 | |
| 1.1.159 | 11 / 3 | |
| 1.1.158 | 11 / 3 | |
| 1.1.157 | 11 / 3 | |
| 1.1.156 | 11 / 3 | |
| 1.1.152 | 11 / 3 | |
| 1.1.151 | 11 / 3 | |
| 1.1.150 | 11 / 3 | |
| 1.1.149 | 11 / 3 | |
| 1.1.148 | 11 / 3 | |
| 1.1.147 | 11 / 3 | |
| 1.1.146 | 11 / 3 | |
| 1.1.145 | 11 / 3 | |
| 1.1.144 | 11 / 3 | |
| 1.1.143 | 11 / 3 | |
| 1.1.142 | 11 / 3 | |
| 1.1.141 | 11 / 3 | |
| 1.1.140 | 11 / 3 | |
| 1.1.138 | 11 / 3 | |
| 1.1.137 | 11 / 3 | |
| 1.1.136 | 11 / 3 | |
| 1.1.135 | 11 / 3 | |
| 1.1.134 | 11 / 3 | |
| 1.1.133 | 11 / 3 |
v1.1.190
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.189
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.188
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.186
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.185
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.184
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.183
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.179
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.177
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.176
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.175
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.172
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.171
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.170
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.167
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.166
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.165
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.159
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.157
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.152
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.151
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.150
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.149
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.148
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.147
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.146
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.145
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.144
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.143
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.142
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.141
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.140
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.138
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.137
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.136
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.135
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.134
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.133
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.