← Home

@uns-kit/core

npm Repository Homepage

Core utilities and runtime building blocks for UNS-based realtime transformers.

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

aljosavistercuaupro

Keywords

unsunified-namespacemqttiottypescriptrealtime

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Package has no CI provenance but is otherwise clean; stable false positive for this package. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped IoT/UNS package; name similarity to 'cors' is coincidental, not impersonation. ai
phantom-deps phantom-dep:fs-extra AI (phantom-deps): fs-extra is listed in dependencies and used in build scripts; phantom-dep heuristic misfires here. ai

Versions (showing 51 of 87)

View all versions
Version Deps Published
3.0.5 19 / 2
3.0.4 19 / 2
3.0.3 19 / 2
3.0.2 19 / 2
3.0.1 19 / 2
3.0.0 19 / 2
2.0.81 19 / 2
2.0.80 19 / 2
2.0.79 19 / 2
2.0.78 19 / 2
2.0.77 19 / 2
2.0.75 19 / 2
2.0.73 19 / 2
2.0.72 19 / 2
2.0.71 19 / 2
2.0.70 19 / 2
2.0.69 19 / 2
2.0.68 19 / 2
2.0.67 19 / 2
2.0.66 19 / 2
2.0.65 19 / 2
2.0.64 19 / 2
2.0.63 19 / 2
2.0.62 19 / 2
2.0.61 19 / 2
2.0.60 19 / 2
2.0.59 19 / 2
2.0.58 19 / 2
2.0.57 19 / 2
2.0.56 19 / 2
2.0.55 19 / 2
2.0.54 19 / 2
2.0.53 19 / 2
2.0.52 19 / 2
2.0.51 19 / 2
2.0.50 19 / 2
2.0.49 19 / 2
2.0.48 19 / 2
2.0.46 19 / 2
2.0.44 19 / 2
2.0.43 19 / 2
2.0.42 19 / 2
2.0.41 19 / 2
2.0.40 19 / 2
2.0.39 19 / 2
2.0.38 19 / 2
2.0.37 19 / 2
2.0.36 19 / 2
2.0.35 19 / 2
2.0.34 19 / 2
2.0.33 19 / 2

v3.0.5

1 finding
INFO No provenance attestation provenance

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

v3.0.4

1 finding
INFO No provenance attestation provenance

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

v3.0.3

1 finding
INFO No provenance attestation provenance

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

v3.0.2

1 finding
INFO No provenance attestation provenance

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

v3.0.1

1 finding
INFO No provenance attestation provenance

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

v3.0.0

1 finding
INFO No provenance attestation provenance

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

v2.0.81

1 finding
INFO No provenance attestation provenance

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

v2.0.80

1 finding
INFO No provenance attestation provenance

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

v2.0.79

1 finding
INFO No provenance attestation provenance

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

v2.0.78

1 finding
INFO No provenance attestation provenance

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

v2.0.77

1 finding
INFO No provenance attestation provenance

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

v2.0.75

1 finding
INFO No provenance attestation provenance

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

v2.0.73

1 finding
INFO No provenance attestation provenance

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

v2.0.72

1 finding
INFO No provenance attestation provenance

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

v2.0.71

2 findings
INFO No provenance attestation provenance

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

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

This version was published by a different npm account (aljosavister) than the most recent previously approved version (cuaupro) on 2026-07-10, 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.70

1 finding
INFO No provenance attestation provenance

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