@kosdev-code/kos-ui-sdk
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:models/utils/service-accessor.d.ts | AI (source-diff): The flagged file is a TypeScript declaration (.d.ts) with a long union type of API endpoint strings — a common codegen pattern, not obfuscated executable code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package has 173 versions and 395 days of history; missing metadata is a consistent characteristic of this SDK, not a malicious signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with 173 versions; missing description is a persistent metadata gap, not a malicious indicator. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() usage is in minified bundle code within an expression/template parser context — a well-known legitimate pattern. Consistent across versions of this SDK. | ai | |
| phantom-deps | phantom-dep:@kosdev-code/kos-api-levels | AI (phantom-deps): Same-org scoped dependency; phantom import is expected for SDK packages that re-export or indirectly use sibling packages. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 3.0.10 | 6 / 0 | |
| 3.0.9 | 6 / 0 | |
| 3.0.8 | 6 / 0 | |
| 3.0.7 | 6 / 0 | |
| 3.0.6 | 6 / 0 | |
| 3.0.5 | 6 / 0 | |
| 3.0.4 | 6 / 0 | |
| 3.0.3 | 6 / 0 | |
| 3.0.2 | 6 / 0 | |
| 3.0.1 | 6 / 0 | |
| 3.0.0 | 6 / 0 | |
| 2.1.40 | 6 / 0 | |
| 2.1.39 | 6 / 0 | |
| 2.1.38 | 6 / 0 | |
| 2.1.37 | 5 / 0 | |
| 2.1.36 | 5 / 0 | |
| 2.1.35 | 5 / 0 | |
| 2.1.34 | 5 / 0 | |
| 2.1.33 | 5 / 0 | |
| 2.1.32 | 5 / 0 | |
| 2.1.31 | 5 / 0 | |
| 2.1.30 | 5 / 0 | |
| 2.1.29 | 5 / 0 | |
| 2.1.28 | 5 / 0 | |
| 2.1.27 | 5 / 0 | |
| 2.1.26 | 5 / 0 | |
| 2.1.25 | 5 / 0 | |
| 2.1.23 | 5 / 0 | |
| 2.1.22 | 5 / 0 | |
| 2.1.21 | 5 / 0 | |
| 2.1.20 | 5 / 0 | |
| 2.1.19 | 5 / 0 | |
| 2.1.18 | 5 / 0 | |
| 2.1.17 | 5 / 0 | |
| 2.1.16 | 5 / 0 | |
| 2.1.15 | 5 / 0 | |
| 2.1.14 | 5 / 0 | |
| 2.1.13 | 5 / 0 | |
| 2.1.12 | 5 / 0 | |
| 2.1.11 | 5 / 0 | |
| 2.1.10 | 5 / 0 | |
| 2.1.9 | 5 / 0 | |
| 2.1.8 | 5 / 0 | |
| 2.1.7 | 5 / 0 | |
| 2.1.6 | 5 / 0 | |
| 2.1.5 | 5 / 0 | |
| 2.1.4 | 5 / 0 | |
| 2.1.3 | 5 / 0 | |
| 2.1.2 | 5 / 0 | |
| 2.1.1 | 5 / 0 | |
| 2.1.0 | 5 / 0 | |
| 2.0.46 | 5 / 0 | |
| 2.0.45 | 6 / 0 | |
| 2.0.44 | 5 / 0 | |
| 2.0.43 | 5 / 0 | |
| 2.0.42 | 5 / 0 | |
| 2.0.41 | 5 / 0 | |
| 2.0.40 | 5 / 0 | |
| 2.0.39 | 5 / 0 | |
| 2.0.38 | 5 / 0 | |
| 2.0.37 | 5 / 0 | |
| 2.0.36 | 5 / 0 | |
| 2.0.35 | 5 / 0 | |
| 2.0.34 | 5 / 0 | |
| 2.0.33 | 5 / 0 | |
| 2.0.32 | 5 / 0 | |
| 2.0.31 | 5 / 0 | |
| 2.0.30 | 5 / 0 | |
| 2.0.29 | 5 / 0 | |
| 2.0.28 | 5 / 0 | |
| 2.0.27 | 5 / 0 | |
| 2.0.26 | 5 / 0 | |
| 2.0.25 | 5 / 0 | |
| 2.0.24 | 5 / 0 | |
| 2.0.23 | 5 / 0 | |
| 2.0.22 | 5 / 0 | |
| 2.0.21 | 5 / 0 | |
| 2.0.20 | 5 / 0 | |
| 2.0.19 | 5 / 0 | |
| 2.0.18 | 5 / 0 | |
| 2.0.17 | 5 / 0 | |
| 2.0.16 | 5 / 0 | |
| 2.0.15 | 5 / 0 | |
| 2.0.12 | 5 / 0 | |
| 2.0.11 | 5 / 0 | |
| 2.0.10 | 5 / 0 | |
| 2.0.9 | 5 / 0 | |
| 2.0.8 | 5 / 0 | |
| 2.0.7 | 5 / 0 | |
| 2.0.6 | 5 / 0 | |
| 2.0.5 | 5 / 0 | |
| 2.0.3 | 5 / 0 | |
| 2.0.2 | 5 / 0 |
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.