@thi.ng/geom-trace-bitmap Apache-2.0 51 versions

@thi.ng/geom-trace-bitmap

npm Repository Homepage

Bitmap image to hairline vector and point cloud conversions

51

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

thi.ng

Keywords

bitmapconversionimagelinepixelpointcloudtracetypescriptvector

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): First-party thi.ng/umbrella sibling dep; stable pattern across all @thi.ng/* packages.	ai	2026/04/29
dependencies	unvetted-dep:@thi.ng/pixel	AI (dependencies): First-party thi.ng/umbrella sibling dep.	ai	2026/04/29
dependencies	unvetted-dep:@thi.ng/vectors	AI (dependencies): First-party thi.ng/umbrella sibling dep.	ai	2026/04/29
dependencies	unvetted-dep:@thi.ng/matrices	AI (dependencies): First-party thi.ng/umbrella sibling dep.	ai	2026/04/29
dependencies	unvetted-dep:@thi.ng/grid-iterators	AI (dependencies): First-party thi.ng/umbrella sibling dep.	ai	2026/04/29

Versions (showing 51 of 52)

View all versions

Version	Deps	Published
0.3.190	6 / 3	2026-06-05
0.3.189	6 / 3	2026-05-23
0.3.188	6 / 3	2026-05-20
0.3.186	6 / 3	2026-05-11
0.3.185	6 / 3	2026-05-08
0.3.183	6 / 3	2026-04-26
0.3.182	6 / 3	2026-04-18
0.3.181	6 / 3	2026-04-09
0.3.180	6 / 3	2026-04-02
0.3.179	6 / 3	2026-03-21
0.3.178	6 / 3	2026-03-19
0.3.177	6 / 3	2026-03-11
0.3.176	6 / 3	2026-03-11
0.3.175	6 / 3	2026-03-08
0.3.174	6 / 3	2026-03-07
0.3.173	6 / 3	2026-03-07
0.3.171	6 / 3	2026-02-07
0.3.170	6 / 3	2026-01-23
0.3.169	6 / 3	2026-01-16
0.3.168	6 / 3	2025-12-25
0.3.167	6 / 3	2025-12-11
0.3.166	6 / 3	2025-12-03
0.3.165	6 / 3	2025-11-25
0.3.164	6 / 3	2025-11-21
0.3.163	6 / 3	2025-11-19
0.3.162	6 / 3	2025-11-13
0.3.161	6 / 3	2025-10-25
0.3.160	6 / 3	2025-10-24
0.3.156	6 / 3	2025-09-25
0.3.155	6 / 3	2025-09-01
0.3.154	6 / 3	2025-08-11
0.3.153	6 / 3	2025-08-07
0.3.152	6 / 3	2025-08-04
0.3.150	6 / 3	2025-07-31
0.3.149	6 / 3	2025-07-30
0.3.148	6 / 3	2025-07-26
0.3.147	6 / 3	2025-07-24
0.3.146	6 / 3	2025-07-21
0.3.144	6 / 3	2025-07-20
0.3.143	6 / 3	2025-07-15
0.3.142	6 / 3	2025-07-14
0.3.141	6 / 3	2025-07-13
0.3.140	6 / 3	2025-07-10
0.3.139	6 / 3	2025-07-09
0.3.138	6 / 3	2025-06-24
0.3.137	6 / 3	2025-06-18
0.3.136	6 / 3	2025-06-14
0.3.135	6 / 3	2025-06-09
0.3.134	6 / 3	2025-05-28
0.3.133	6 / 3	2025-05-18
0.3.132	6 / 3	2025-05-02

v0.3.190

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.189

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.188

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.186

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.185

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.183

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.182

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.181

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.179

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.178

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.177

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO OSV query failed osv

Connection reset

v0.3.176

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.175

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.174

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.173

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.171

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.170

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.169

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.168

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.167

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.166

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.165

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.164

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.163

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.162

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.161

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.160

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.156

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.155

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.154

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.153

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.152

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.150

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.149

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.148

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.147

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.146

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.144

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.143

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.142

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.141

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.140

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.139

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.138

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.137

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.136

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.135

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.134

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.133

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.132

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.