@thi.ng/transducers-async Apache-2.0 43 versions

@thi.ng/transducers-async

npm Repository Homepage

Async versions of various highly composable transducers, reducers and iterators

43

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

asynccompositioncyclefunctionalgeneratorinfiniteiteratorlazymultitaskingpartitionpipelinereducerstreamthrottletimetransducertransformationtypescript

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 from same thi.ng/umbrella monorepo publisher; stable false positive.	ai	2026/04/29
dependencies	unvetted-dep:@thi.ng/buffers	AI (dependencies): Sibling package from same thi.ng/umbrella monorepo publisher; stable false positive.	ai	2026/04/29
dependencies	unvetted-dep:@thi.ng/compose	AI (dependencies): Sibling package from same thi.ng/umbrella monorepo publisher; stable false positive.	ai	2026/04/29
dependencies	unvetted-dep:@thi.ng/transducers	AI (dependencies): Sibling package from same thi.ng/umbrella monorepo publisher; stable false positive.	ai	2026/04/29

Versions (showing 43 of 43)

Version	Deps	Published
0.5.8	7 / 3	2026-06-05
0.5.7	7 / 3	2026-05-23
0.5.6	7 / 3	2026-05-20
0.5.4	7 / 3	2026-05-11
0.5.3	7 / 3	2026-05-08
0.5.1	7 / 3	2026-04-26
0.5.0	7 / 3	2026-04-18
0.4.49	7 / 3	2026-04-02
0.4.48	7 / 3	2026-03-19
0.4.47	7 / 3	2026-03-11
0.4.46	7 / 3	2026-03-11
0.4.45	7 / 3	2026-03-08
0.4.44	7 / 3	2026-03-07
0.4.43	7 / 3	2026-03-07
0.4.41	7 / 3	2026-02-07
0.4.40	7 / 3	2026-01-23
0.4.39	7 / 3	2026-01-16
0.4.38	7 / 3	2025-12-25
0.4.37	7 / 3	2025-12-03
0.4.36	7 / 3	2025-11-25
0.4.35	7 / 3	2025-11-21
0.4.34	7 / 3	2025-11-13
0.4.33	7 / 3	2025-10-25
0.4.32	7 / 3	2025-10-24
0.4.28	7 / 3	2025-09-25
0.4.27	7 / 3	2025-09-01
0.4.26	7 / 3	2025-08-11
0.4.25	7 / 3	2025-08-07
0.4.24	7 / 3	2025-08-04
0.4.23	7 / 3	2025-08-04
0.4.22	7 / 3	2025-07-30
0.4.21	7 / 3	2025-07-21
0.4.20	7 / 3	2025-07-20
0.4.19	7 / 3	2025-07-15
0.4.18	7 / 3	2025-07-13
0.4.17	7 / 3	2025-07-10
0.4.16	7 / 3	2025-07-09
0.4.15	7 / 3	2025-06-24
0.4.14	7 / 3	2025-06-18
0.4.13	7 / 3	2025-06-14
0.4.12	7 / 3	2025-06-09
0.4.11	7 / 3	2025-05-28
0.4.10	7 / 3	2025-04-30

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.48

1 finding

LOW No provenance attestation provenance

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

v0.4.47

1 finding

LOW No provenance attestation provenance

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

v0.4.46

1 finding

LOW No provenance attestation provenance

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

v0.4.45

1 finding

LOW No provenance attestation provenance

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

v0.4.44

1 finding

LOW No provenance attestation provenance

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

v0.4.43

1 finding

LOW No provenance attestation provenance

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

v0.4.41

1 finding

LOW No provenance attestation provenance

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

v0.4.40

1 finding

LOW No provenance attestation provenance

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

v0.4.39

1 finding

LOW No provenance attestation provenance

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

v0.4.38

1 finding

LOW No provenance attestation provenance

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

v0.4.37

1 finding

LOW No provenance attestation provenance

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

v0.4.36

1 finding

LOW No provenance attestation provenance

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

v0.4.35

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

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

1 finding

LOW No provenance attestation provenance

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

v0.4.32

1 finding

LOW No provenance attestation provenance

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

v0.4.28

1 finding

LOW No provenance attestation provenance

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

v0.4.27

1 finding

LOW No provenance attestation provenance

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

v0.4.26

1 finding

LOW No provenance attestation provenance

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

v0.4.25

1 finding

LOW No provenance attestation provenance

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

v0.4.24

1 finding

LOW No provenance attestation provenance

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

v0.4.23

1 finding

LOW No provenance attestation provenance

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

v0.4.22

1 finding

LOW No provenance attestation provenance

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

v0.4.21

1 finding

LOW No provenance attestation provenance

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

v0.4.20

1 finding

LOW No provenance attestation provenance

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

v0.4.19

1 finding

LOW No provenance attestation provenance

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

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.17

1 finding

LOW No provenance attestation provenance

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

v0.4.16

1 finding

LOW No provenance attestation provenance

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

v0.4.15

1 finding

LOW No provenance attestation provenance

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

v0.4.14

1 finding

LOW No provenance attestation provenance

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

v0.4.13

1 finding

LOW No provenance attestation provenance

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

v0.4.12

1 finding

LOW No provenance attestation provenance

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

v0.4.11

1 finding

LOW No provenance attestation provenance

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

v0.4.10

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.