printable-characters Unlicense 40 versions

printable-characters

npm Repository Homepage

A little helper for handling strings containing zero width control characters, ANSI styling, whitespaces, newlines, 💩, etc.

40

Versions

Unlicense

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

xpl

Keywords

string widthstring lengthreal string widthreal string lengthoptical string widthprinted widthunicodecodepointscode pointsstrlenzero widthzero width symbolszero width charactersvisible charactersvisible symbolsvisibleinvisibleinvisible symbolsinvisible charactersprintableprintable lengthprintable symbolsprintable charactersnon-printable charactersnonprintable characterscharacterssymbolsstring lengthreal string lengthstring trimmingtrimmingescapesescape codescodesansi escapestokenizingansiwhitespaces

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:build/printable-characters.js	AI (source-diff): Babel-transpiled build output of the package's own source; long lines are minification, not obfuscation.	ai	2026/07/20
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in test.js uses an env var set explicitly in package.json test scripts to point to the package's own build output. This is a stable, benign test harness pattern for this package.	ai	2026/04/25

Versions (showing 40 of 40)

Version	Deps	Published
1.0.42	0 / 8	2018-07-16
1.0.39	0 / 8	2018-04-29
1.0.38	0 / 8	2017-10-07
1.0.37	0 / 8	2017-10-07
1.0.36	0 / 8	2017-10-07
1.0.35	0 / 8	2017-10-07
1.0.34	0 / 8	2017-10-07
1.0.33	0 / 8	2017-09-27
1.0.32	0 / 8	2017-09-27
1.0.31	0 / 8	2017-09-27
1.0.30	0 / 7	2017-09-27
1.0.29	0 / 5	2017-09-27
1.0.28	0 / 5	2017-07-23
1.0.27	0 / 5	2017-07-23
1.0.26	0 / 6	2017-07-22
1.0.25	0 / 6	2017-07-22
1.0.24	0 / 6	2017-07-22
1.0.23	0 / 6	2017-07-22
1.0.22	0 / 6	2017-07-22
1.0.21	0 / 6	2017-07-22
1.0.20	0 / 6	2017-07-22
1.0.18	0 / 6	2017-07-21
1.0.17	0 / 2	2017-07-20
1.0.16	0 / 2	2017-07-20
1.0.15	0 / 2	2017-07-20
1.0.14	0 / 2	2017-07-01
1.0.13	0 / 2	2017-07-01
1.0.12	0 / 2	2017-07-01
1.0.11	0 / 2	2017-07-01
1.0.10	0 / 2	2017-07-01
1.0.9	0 / 2	2017-07-01
1.0.8	0 / 2	2017-07-01
1.0.7	0 / 2	2017-07-01
1.0.6	0 / 2	2017-07-01
1.0.5	0 / 2	2017-07-01
1.0.4	0 / 2	2017-06-30
1.0.3	0 / 2	2017-06-30
1.0.2	0 / 2	2017-06-30
1.0.1	0 / 2	2017-06-30
1.0.0	0 / 2	2017-06-30

v1.0.39

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.38

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.37

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.36

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.35

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.34

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.33

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.32

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.31

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.30

2 findings

HIGH New obfuscated file: build/printable-characters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.29

1 finding

LOW No provenance attestation provenance

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

v1.0.28

1 finding

LOW No provenance attestation provenance

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

v1.0.27

1 finding

LOW No provenance attestation provenance

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

v1.0.26

1 finding

LOW No provenance attestation provenance

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

v1.0.25

1 finding

LOW No provenance attestation provenance

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

v1.0.24

1 finding

LOW No provenance attestation provenance

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

v1.0.23

1 finding

LOW No provenance attestation provenance

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

v1.0.22

1 finding

LOW No provenance attestation provenance

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

v1.0.21

1 finding

LOW No provenance attestation provenance

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

v1.0.20

1 finding

LOW No provenance attestation provenance

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

v1.0.18

1 finding

LOW No provenance attestation provenance

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

v1.0.17

1 finding

LOW No provenance attestation provenance

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

v1.0.16

1 finding

LOW No provenance attestation provenance

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

v1.0.15

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

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.

v1.0.0

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.