@thi.ng/proctext
Extensible procedural text generation engine with dynamic, mutable state, indirection, randomizable & recursive variable expansions
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): Internal thi.ng/umbrella monorepo dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/parse | AI (dependencies): Internal thi.ng/umbrella monorepo dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/arrays | AI (dependencies): Internal thi.ng/umbrella monorepo dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/random | AI (dependencies): Internal thi.ng/umbrella monorepo dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/strings | AI (dependencies): Internal thi.ng/umbrella monorepo dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/defmulti | AI (dependencies): Internal thi.ng/umbrella monorepo dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/object-utils | AI (dependencies): Internal thi.ng/umbrella monorepo dep; same trusted publisher. | ai | |
| provenance | no-provenance | AI (provenance): thi.ng/umbrella does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 1.0.70 | 9 / 3 | |
| 1.0.69 | 9 / 3 | |
| 1.0.68 | 9 / 3 | |
| 1.0.66 | 9 / 3 | |
| 1.0.65 | 9 / 3 | |
| 1.0.63 | 9 / 3 | |
| 1.0.62 | 9 / 3 | |
| 1.0.61 | 9 / 3 | |
| 1.0.60 | 9 / 3 | |
| 1.0.59 | 9 / 3 | |
| 1.0.58 | 9 / 3 | |
| 1.0.57 | 9 / 3 | |
| 1.0.56 | 9 / 3 | |
| 1.0.55 | 9 / 3 | |
| 1.0.54 | 9 / 3 | |
| 1.0.52 | 9 / 3 | |
| 1.0.51 | 9 / 3 | |
| 1.0.50 | 9 / 3 | |
| 1.0.49 | 9 / 3 | |
| 1.0.48 | 9 / 3 | |
| 1.0.47 | 9 / 3 | |
| 1.0.46 | 9 / 3 | |
| 1.0.45 | 9 / 3 | |
| 1.0.44 | 9 / 3 | |
| 1.0.43 | 9 / 3 | |
| 1.0.39 | 9 / 3 | |
| 1.0.38 | 9 / 3 | |
| 1.0.37 | 9 / 3 | |
| 1.0.36 | 9 / 3 | |
| 1.0.35 | 9 / 3 | |
| 1.0.34 | 9 / 3 | |
| 1.0.33 | 9 / 3 | |
| 1.0.31 | 9 / 3 | |
| 1.0.30 | 9 / 3 | |
| 1.0.29 | 9 / 3 | |
| 1.0.28 | 9 / 3 | |
| 1.0.27 | 9 / 3 | |
| 1.0.26 | 9 / 3 | |
| 1.0.25 | 9 / 3 | |
| 1.0.24 | 9 / 3 | |
| 1.0.23 | 9 / 3 | |
| 1.0.22 | 9 / 3 | |
| 1.0.21 | 9 / 3 | |
| 1.0.20 | 9 / 3 | |
| 1.0.19 | 9 / 3 | |
| 1.0.18 | 9 / 3 |
v1.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
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.0.45
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.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
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.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.