@thi.ng/wasm-api Apache-2.0 42 versions

@thi.ng/wasm-api

npm Repository Homepage

Generic, modular, extensible API bridge and infrastructure for hybrid JS & WebAssembly projects

42

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

allocatorapibigintbindingsbrowserceventfree-listhexinteroploggermemorymemory-mappedmodularpolyglotshared-memorystringtypedarraytypescriptutf8wasmzig

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

Versions (showing 42 of 42)

Version	Deps	Published
2.4.32	7 / 3	2026-06-05
2.4.31	7 / 3	2026-05-23
2.4.30	7 / 3	2026-05-20
2.4.28	7 / 3	2026-05-11
2.4.27	7 / 3	2026-05-08
2.4.25	7 / 3	2026-04-26
2.4.24	7 / 3	2026-04-18
2.4.23	7 / 3	2026-04-02
2.4.22	7 / 3	2026-03-19
2.4.21	7 / 3	2026-03-11
2.4.20	7 / 3	2026-03-08
2.4.19	7 / 3	2026-03-07
2.4.18	7 / 3	2026-03-07
2.4.16	7 / 3	2026-02-07
2.4.15	7 / 3	2026-01-23
2.4.14	7 / 3	2026-01-16
2.4.13	7 / 3	2025-12-25
2.4.12	7 / 3	2025-12-03
2.4.11	7 / 3	2025-11-25
2.4.10	7 / 3	2025-11-21
2.4.9	7 / 3	2025-11-13
2.4.8	7 / 3	2025-10-25
2.4.7	7 / 3	2025-10-24
2.4.3	7 / 3	2025-10-07
2.4.2	7 / 3	2025-09-25
2.4.1	7 / 3	2025-09-02
2.4.0	7 / 3	2025-09-01
2.3.31	7 / 3	2025-08-11
2.3.30	7 / 3	2025-08-07
2.3.29	7 / 3	2025-08-04
2.3.28	7 / 3	2025-08-04
2.3.27	7 / 3	2025-07-30
2.3.26	7 / 3	2025-07-21
2.3.25	7 / 3	2025-07-20
2.3.24	7 / 3	2025-07-15
2.3.23	7 / 3	2025-07-10
2.3.22	7 / 3	2025-06-24
2.3.21	7 / 3	2025-06-18
2.3.20	7 / 3	2025-06-14
2.3.19	7 / 3	2025-06-09
2.3.18	7 / 3	2025-05-28
2.3.17	7 / 3	2025-04-30

v2.4.32

1 finding

LOW No provenance attestation provenance

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

v2.4.31

1 finding

LOW No provenance attestation provenance

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

v2.4.30

1 finding

LOW No provenance attestation provenance

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

v2.4.28

1 finding

LOW No provenance attestation provenance

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

v2.4.27

1 finding

LOW No provenance attestation provenance

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

v2.4.25

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.

v2.4.24

1 finding

LOW No provenance attestation provenance

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

v2.4.22

1 finding

LOW No provenance attestation provenance

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

v2.4.21

1 finding

LOW No provenance attestation provenance

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

v2.4.20

1 finding

LOW No provenance attestation provenance

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

v2.4.19

1 finding

LOW No provenance attestation provenance

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

v2.4.18

1 finding

LOW No provenance attestation provenance

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

v2.4.16

1 finding

LOW No provenance attestation provenance

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

v2.4.15

1 finding

LOW No provenance attestation provenance

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

v2.4.14

1 finding

LOW No provenance attestation provenance

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

v2.4.13

1 finding

LOW No provenance attestation provenance

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

v2.4.12

1 finding

LOW No provenance attestation provenance

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

v2.4.11

1 finding

LOW No provenance attestation provenance

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

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

v2.4.9

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.

v2.4.8

1 finding

LOW No provenance attestation provenance

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

v2.4.7

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.31

1 finding

LOW No provenance attestation provenance

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

v2.3.30

1 finding

LOW No provenance attestation provenance

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

v2.3.29

1 finding

LOW No provenance attestation provenance

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

v2.3.28

1 finding

LOW No provenance attestation provenance

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

v2.3.27

1 finding

LOW No provenance attestation provenance

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

v2.3.26

1 finding

LOW No provenance attestation provenance

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

v2.3.25

1 finding

LOW No provenance attestation provenance

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

v2.3.24

1 finding

LOW No provenance attestation provenance

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

v2.3.23

1 finding

LOW No provenance attestation provenance

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

v2.3.22

1 finding

LOW No provenance attestation provenance

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

v2.3.21

1 finding

LOW No provenance attestation provenance

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

v2.3.20

1 finding

LOW No provenance attestation provenance

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

v2.3.19

1 finding

LOW No provenance attestation provenance

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

v2.3.18

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.

v2.3.17

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.