@unisphere/genie-types
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @unisphere sibling package, not an external supply-chain risk. | ai | |
| dependencies | unvetted-dep:@unisphere/ui-i18n-react | AI (dependencies): Same-org sibling dependency in Kaltura's unisphere monorepo, consistent pattern with other accepted deps. | ai | |
| dependencies | unvetted-dep:@kaltura-corp/unisphere-rtc-core | AI (dependencies): Internal Kaltura-org scoped dep matching package's own ecosystem; stable across versions. | ai | |
| dependencies | unvetted-dep:@kaltura-sdk/rtc-core | AI (dependencies): Related first-party Kaltura SDK dep, consistent across versions. | ai | |
| dependencies | unvetted-dep:@unisphere/runtime-js | AI (dependencies): Same-org internal dependency, consistent with monorepo package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; low risk for this internal Kaltura package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions; internal types package from known org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Kaltura types package; sparse README is expected for org-internal tooling, not a spam/phishing indicator. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.25.1 | 5 / 0 | |
| 1.24.2 | 4 / 0 | |
| 1.24.1 | 4 / 0 | |
| 1.23.2 | 4 / 0 | |
| 1.23.1 | 4 / 0 | |
| 1.23.0 | 4 / 0 | |
| 1.21.0 | 3 / 0 | |
| 1.20.0 | 3 / 0 | |
| 1.18.0 | 3 / 0 | |
| 1.16.1 | 3 / 0 | |
| 1.16.0 | 3 / 0 | |
| 1.14.0 | 3 / 0 | |
| 1.13.2 | 3 / 0 | |
| 1.13.1 | 3 / 0 | |
| 1.13.0 | 3 / 0 | |
| 1.11.0 | 3 / 0 | |
| 1.10.0 | 3 / 0 | |
| 1.9.0 | 3 / 0 | |
| 1.8.3 | 5 / 0 | |
| 1.8.2 | 5 / 0 |
v1.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.