@uns-kit/api MIT 51 versions

@uns-kit/api

npm Repository Homepage

Express-powered API gateway plugin for UnsProxyProcess with JWT/JWKS support.

51

Versions

MIT

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

aljosavistercuaupro

Keywords

unsapiexpresshttpmqtttypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:uuid	AI (phantom-deps): uuid is a well-known package; phantom-dep likely fires due to config-level reference rather than missing import.	ai	2026/05/27
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped monorepo package @uns-kit/api; Levenshtein match to 'hapi' is coincidental substring, not impersonation.	ai	2026/05/07
typosquat	typosquat.levenshtein:pg	AI (typosquat): Same scoped monorepo; no relation to pg postgres driver.	ai	2026/05/07
typosquat	typosquat.levenshtein:joi	AI (typosquat): Same scoped monorepo; no relation to joi validation library.	ai	2026/05/07
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Same scoped monorepo; no relation to ajv JSON schema validator.	ai	2026/05/07

Versions (showing 51 of 80)

View all versions

Version	Deps	Published
2.0.59	7 / 4	2026-06-02
2.0.58	7 / 4	2026-06-02
2.0.57	7 / 4	2026-06-02
2.0.56	7 / 4	2026-06-01
2.0.55	7 / 4	2026-06-01
2.0.53	7 / 4	2026-05-26
2.0.52	7 / 4	2026-05-26
2.0.51	7 / 4	2026-05-21
2.0.50	7 / 4	2026-05-21
2.0.48	7 / 4	2026-05-21
2.0.46	7 / 4	2026-05-19
2.0.44	5 / 4	2026-05-04
2.0.43	5 / 4	2026-05-04
2.0.41	5 / 4	2026-05-01
2.0.39	5 / 4	2026-04-12
2.0.38	5 / 4	2026-04-12
2.0.37	5 / 4	2026-04-09
2.0.36	5 / 4	2026-04-09
2.0.35	5 / 4	2026-04-09
2.0.34	5 / 4	2026-04-07
2.0.33	5 / 4	2026-04-06
2.0.32	5 / 4	2026-04-06
2.0.31	5 / 4	2026-04-06
2.0.30	5 / 4	2026-04-03
2.0.29	5 / 4	2026-03-31
2.0.28	5 / 4	2026-03-31
2.0.25	5 / 4	2026-03-29
2.0.24	5 / 4	2026-03-29
2.0.21	5 / 4	2026-03-22
2.0.20	5 / 4	2026-03-22
2.0.19	5 / 4	2026-03-19
2.0.18	5 / 4	2026-03-18
2.0.17	5 / 4	2026-03-11
2.0.16	5 / 4	2026-02-15
2.0.15	5 / 4	2026-02-14
2.0.14	5 / 4	2026-02-10
2.0.13	5 / 4	2026-02-04
2.0.11	5 / 4	2026-01-27
2.0.10	5 / 4	2026-01-27
2.0.9	5 / 4	2026-01-27
2.0.8	5 / 4	2026-01-23
2.0.7	5 / 4	2026-01-23
2.0.6	5 / 4	2026-01-23
2.0.5	5 / 4	2026-01-23
2.0.4	5 / 4	2026-01-23
2.0.3	5 / 4	2026-01-23
2.0.1	5 / 4	2026-01-23
2.0.0	5 / 4	2026-01-21
0.0.55	5 / 4	2026-01-20
0.0.54	5 / 4	2026-01-20
0.0.53	5 / 4	2026-01-19

v2.0.59

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: cuaupro → aljosavister (on 2026-06-02, known maintainer) provenance

This version was published by a different npm account (aljosavister) than the most recent previously approved version (cuaupro) on 2026-06-02, but aljosavister is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.58

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: cuaupro → aljosavister (on 2026-06-02, known maintainer) provenance

This version was published by a different npm account (aljosavister) than the most recent previously approved version (cuaupro) on 2026-06-02, but aljosavister is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.57

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: aljosavister → cuaupro (on 2026-06-02, known maintainer) provenance

This version was published by a different npm account (cuaupro) than the most recent previously approved version (aljosavister) on 2026-06-02, but cuaupro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.56

1 finding

LOW No provenance attestation provenance

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

v2.0.55

1 finding

LOW No provenance attestation provenance

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

v2.0.53

1 finding

LOW No provenance attestation provenance

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

v2.0.52

1 finding

LOW No provenance attestation provenance

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

v2.0.51

1 finding

LOW No provenance attestation provenance

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

v2.0.50

1 finding

LOW No provenance attestation provenance

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

v2.0.48

1 finding

LOW No provenance attestation provenance

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

v2.0.46

1 finding

LOW No provenance attestation provenance

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

v2.0.44

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@uns-kit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@uns-kit/api' is 1 edit(s) away from popular package 'hapi'.

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

1 finding

LOW No provenance attestation provenance

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

v2.0.39

1 finding

LOW No provenance attestation provenance

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

v2.0.38

1 finding

LOW No provenance attestation provenance

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

v2.0.37

1 finding

LOW No provenance attestation provenance

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

v2.0.36

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@uns-kit/api' is 1 edit(s) away from popular package 'hapi'.

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

1 finding

LOW No provenance attestation provenance

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

v2.0.34

1 finding

LOW No provenance attestation provenance

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

v2.0.33

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@uns-kit/api' is 1 edit(s) away from popular package 'hapi'.

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

1 finding

LOW No provenance attestation provenance

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

v2.0.31

1 finding

LOW No provenance attestation provenance

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

v2.0.30

1 finding

LOW No provenance attestation provenance

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

v2.0.29

1 finding

LOW No provenance attestation provenance

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

v2.0.28

1 finding

LOW No provenance attestation provenance

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

v2.0.25

1 finding

LOW No provenance attestation provenance

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

v2.0.24

1 finding

LOW No provenance attestation provenance

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

v2.0.21

1 finding

LOW No provenance attestation provenance

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

v2.0.20

1 finding

LOW No provenance attestation provenance

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

v2.0.19

1 finding

LOW No provenance attestation provenance

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

v2.0.18

1 finding

LOW No provenance attestation provenance

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

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

1 finding

LOW No provenance attestation provenance

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

v2.0.14

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v0.0.55

1 finding

LOW No provenance attestation provenance

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

v0.0.54

1 finding

LOW No provenance attestation provenance

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

v0.0.53

1 finding

LOW No provenance attestation provenance

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