@unisphere/runtime
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Scoped org package; missing description is a style issue, not a risk signal for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Kaltura internal scoped package; sparse metadata is expected, not indicative of spam/malice. | ai | |
| provenance | no-provenance | AI (provenance): Established Kaltura org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 94 of 94)
| Version | Deps | Published |
|---|---|---|
| 1.99.0 | 1 / 0 | |
| 1.98.0 | 1 / 0 | |
| 1.97.0 | 1 / 0 | |
| 1.96.2 | 1 / 0 | |
| 1.96.1 | 1 / 0 | |
| 1.96.0 | 1 / 0 | |
| 1.95.0 | 1 / 0 | |
| 1.94.0 | 1 / 0 | |
| 1.93.2 | 1 / 0 | |
| 1.93.1 | 1 / 0 | |
| 1.93.0 | 1 / 0 | |
| 1.92.0 | 1 / 0 | |
| 1.91.0 | 1 / 0 | |
| 1.90.1 | 1 / 0 | |
| 1.90.0 | 1 / 0 | |
| 1.89.2 | 1 / 0 | |
| 1.89.1 | 1 / 0 | |
| 1.89.0 | 1 / 0 | |
| 1.88.0 | 1 / 0 | |
| 1.87.3 | 1 / 0 | |
| 1.87.2 | 1 / 0 | |
| 1.87.1 | 1 / 0 | |
| 1.87.0 | 1 / 0 | |
| 1.86.2 | 1 / 0 | |
| 1.86.1 | 1 / 0 | |
| 1.86.0 | 1 / 0 | |
| 1.85.2 | 1 / 0 | |
| 1.85.1 | 1 / 0 | |
| 1.85.0 | 1 / 0 | |
| 1.84.1 | 1 / 0 | |
| 1.84.0 | 1 / 0 | |
| 1.83.0 | 1 / 0 | |
| 1.82.0 | 1 / 0 | |
| 1.81.0 | 0 / 0 | |
| 1.80.0 | 0 / 0 | |
| 1.78.4 | 0 / 0 | |
| 1.78.3 | 0 / 0 | |
| 1.78.2 | 0 / 0 | |
| 1.78.0 | 0 / 0 | |
| 1.77.0 | 0 / 0 | |
| 1.76.1 | 0 / 0 | |
| 1.76.0 | 0 / 0 | |
| 1.75.8 | 0 / 0 | |
| 1.75.7 | 0 / 0 | |
| 1.75.5 | 0 / 0 | |
| 1.75.4 | 0 / 0 | |
| 1.75.0 | 0 / 0 | |
| 1.74.0 | 0 / 0 | |
| 1.73.0 | 0 / 0 | |
| 1.72.0 | 0 / 0 | |
| 1.71.0 | 0 / 0 | |
| 1.70.2 | 0 / 0 | |
| 1.70.1 | 0 / 0 | |
| 1.70.0 | 0 / 0 | |
| 1.69.0 | 0 / 0 | |
| 1.68.0 | 0 / 0 | |
| 1.67.0 | 0 / 0 | |
| 1.66.2 | 0 / 0 | |
| 1.66.1 | 0 / 0 | |
| 1.66.0 | 0 / 0 | |
| 1.65.1 | 0 / 0 | |
| 1.65.0 | 0 / 0 | |
| 1.64.0 | 0 / 0 | |
| 1.63.1 | 0 / 0 | |
| 1.63.0 | 0 / 0 | |
| 1.62.3 | 0 / 0 | |
| 1.62.2 | 0 / 0 | |
| 1.62.0 | 0 / 0 | |
| 1.61.1 | 0 / 0 | |
| 1.61.0 | 0 / 0 | |
| 1.60.1 | 0 / 0 | |
| 1.60.0 | 0 / 0 | |
| 1.59.1 | 0 / 0 | |
| 1.59.0 | 0 / 0 | |
| 1.58.0 | 0 / 0 | |
| 1.57.0 | 0 / 0 | |
| 1.56.0 | 0 / 0 | |
| 1.55.0 | 0 / 0 | |
| 1.54.1 | 0 / 0 | |
| 1.54.0 | 0 / 0 | |
| 1.53.0 | 0 / 0 | |
| 1.52.1 | 0 / 0 | |
| 1.52.0 | 0 / 0 | |
| 1.49.0 | 0 / 0 | |
| 1.48.0 | 0 / 0 | |
| 1.47.0 | 0 / 0 | |
| 1.46.0 | 0 / 0 | |
| 1.45.0 | 0 / 0 | |
| 1.44.0 | 0 / 0 | |
| 1.43.0 | 0 / 0 | |
| 1.40.4 | 0 / 0 | |
| 1.40.3 | 0 / 0 | |
| 1.40.2 | 0 / 0 | |
| 1.40.0 | 0 / 0 |
v1.99.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.67.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.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.
v1.66.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.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.
v1.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.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.
v1.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.