← Home

@freik/text

npm Repository Homepage

Some simple text helper functions

10
Versions
Unlicense
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

freik

Keywords

js-utils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:next AI (typosquat): Scoped package @freik/text; 'text' vs 'next' is a coincidental Levenshtein match, not a typosquat. ai
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped package @freik/text; no impersonation of nuxt. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped package @freik/text; no impersonation of jest. ai

Versions (showing 10 of 10)

Version Deps Published
0.5.10 0 / 9
0.5.9 0 / 9
0.5.7 0 / 9
0.5.6 0 / 9
0.5.5 0 / 9
0.5.2 0 / 9
0.5.1 0 / 9
0.3.21 0 / 9
0.3.20 0 / 9
0.3.19 0 / 9

v0.5.10

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@freik/text' is 1 edit(s) away from popular package 'next'.

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.5.9

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@freik/text' is 1 edit(s) away from popular package 'next'.

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.5.7

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@freik/text' is 1 edit(s) away from popular package 'next'.

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.5.6

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@freik/text' is 1 edit(s) away from popular package 'next'.

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.5.5

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@freik/text' is 1 edit(s) away from popular package 'next'.

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.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.3.21

1 finding
LOW No provenance attestation provenance

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

v0.3.20

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.19

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.