@thi.ng/text-canvas
Text based canvas, drawing, plotting, tables with arbitrary formatting (incl. ANSI/HTML)
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): Sibling package in the thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/math | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/arrays | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/strings | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/text-format | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-clip-line | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable false positive for this package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 3.0.125 | 9 / 3 | |
| 3.0.124 | 9 / 3 | |
| 3.0.123 | 9 / 3 | |
| 3.0.121 | 9 / 3 | |
| 3.0.120 | 9 / 3 | |
| 3.0.118 | 9 / 3 | |
| 3.0.117 | 9 / 3 | |
| 3.0.116 | 9 / 3 | |
| 3.0.115 | 9 / 3 | |
| 3.0.114 | 9 / 3 | |
| 3.0.113 | 9 / 3 | |
| 3.0.112 | 9 / 3 | |
| 3.0.111 | 9 / 3 | |
| 3.0.110 | 9 / 3 | |
| 3.0.109 | 9 / 3 | |
| 3.0.108 | 9 / 3 | |
| 3.0.106 | 9 / 3 | |
| 3.0.105 | 9 / 3 | |
| 3.0.104 | 9 / 3 | |
| 3.0.103 | 9 / 3 | |
| 3.0.102 | 9 / 3 | |
| 3.0.101 | 9 / 3 | |
| 3.0.100 | 9 / 3 | |
| 3.0.99 | 9 / 3 | |
| 3.0.98 | 9 / 3 | |
| 3.0.97 | 9 / 3 | |
| 3.0.96 | 9 / 3 | |
| 3.0.92 | 9 / 3 | |
| 3.0.91 | 9 / 3 | |
| 3.0.90 | 9 / 3 | |
| 3.0.89 | 9 / 3 | |
| 3.0.88 | 9 / 3 | |
| 3.0.87 | 9 / 3 | |
| 3.0.86 | 9 / 3 | |
| 3.0.85 | 9 / 3 | |
| 3.0.84 | 9 / 3 | |
| 3.0.83 | 9 / 3 | |
| 3.0.82 | 9 / 3 | |
| 3.0.80 | 9 / 3 | |
| 3.0.79 | 9 / 3 | |
| 3.0.78 | 9 / 3 | |
| 3.0.77 | 9 / 3 | |
| 3.0.76 | 9 / 3 | |
| 3.0.75 | 9 / 4 | |
| 3.0.74 | 9 / 4 | |
| 3.0.73 | 9 / 4 | |
| 3.0.72 | 9 / 4 | |
| 3.0.71 | 9 / 4 | |
| 3.0.70 | 9 / 4 | |
| 3.0.69 | 9 / 4 | |
| 3.0.68 | 9 / 4 |
v3.0.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.