@sofie-automation/shared-lib
Library for types & values shared by core, workers and gateways
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mos-connection/model | AI (dependencies): @mos-connection/model is a known MOS protocol library integral to the Sofie ecosystem; stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clear repo; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.52.0 | 4 / 0 | |
| 1.51.7 | 4 / 0 | |
| 1.51.6 | 4 / 0 | |
| 1.51.5 | 4 / 0 | |
| 1.51.3 | 4 / 0 | |
| 1.51.2 | 4 / 0 | |
| 1.51.1 | 4 / 0 | |
| 1.51.0 | 4 / 0 | |
| 1.50.5 | 4 / 0 | |
| 1.50.4 | 4 / 0 | |
| 1.50.3 | 4 / 0 | |
| 1.50.2 | 4 / 0 |
v1.51.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.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.50.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.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.50.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.