@uns-kit/core
Core utilities and runtime building blocks for UNS-based realtime transformers.
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 |
|---|---|---|---|---|
| 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 61)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 2.0.32 | 19 / 2 | |
| 2.0.31 | 19 / 2 | |
| 2.0.30 | 19 / 2 | |
| 2.0.29 | 19 / 2 | |
| 2.0.28 | 19 / 2 | |
| 2.0.27 | 19 / 2 | |
| 2.0.26 | 19 / 2 | |
| 2.0.25 | 19 / 2 | |
| 2.0.24 | 19 / 2 | |
| 2.0.23 | 19 / 2 | |
| 2.0.22 | 19 / 2 | |
| 2.0.21 | 18 / 2 | |
| 2.0.20 | 18 / 2 | |
| 2.0.19 | 18 / 2 | |
| 2.0.18 | 18 / 2 | |
| 2.0.17 | 18 / 2 | |
| 2.0.16 | 18 / 2 | |
| 2.0.15 | 18 / 2 | |
| 2.0.14 | 18 / 2 | |
| 2.0.13 | 18 / 2 | |
| 2.0.11 | 18 / 2 | |
| 2.0.10 | 18 / 2 | |
| 2.0.9 | 18 / 2 | |
| 2.0.8 | 18 / 2 | |
| 2.0.7 | 18 / 2 | |
| 2.0.6 | 18 / 2 |
v2.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.58
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
2 findingsPackage name '@uns-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.41
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aljosavister) than the most recent previously approved version (cuaupro) on 2026-05-01, 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.40
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cuaupro) than the most recent previously approved version (aljosavister) on 2026-04-17, 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.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
2 findingsPackage name '@uns-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
2 findingsPackage name '@uns-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
2 findingsPackage name '@uns-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.31
2 findingsPackage name '@uns-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.30
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aljosavister) than the most recent previously approved version (cuaupro) on 2026-04-03, 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.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cuaupro) than the most recent previously approved version (aljosavister) on 2026-03-30, 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.26
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cuaupro) than the most recent previously approved version (aljosavister) on 2026-03-30, 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.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cuaupro) than the most recent previously approved version (aljosavister) on 2026-03-24, 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.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cuaupro) than the most recent previously approved version (aljosavister) on 2026-03-23, 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.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.