← Home

@signageos/front-display

npm Repository Homepage

This library contains all the shared code that is common across all platforms (application types). It includes the business logic necessary for communicating with the `signageOS` platform service.

26
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

misak113kytartpetrbilysignageos.iovasekboch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/osd/index.js AI (source-diff): Encoded strings are minified React/scheduler bundle output, not obfuscation. ai
source-diff encoded-string-file:dist/bundle.js AI (source-diff): dist/bundle.js is the expected esbuild minified output; long encoded strings are normal in bundled front-end code. ai
publish-pattern dormant-publish AI (publish-pattern): Established 2443-day-old package with 224 versions; dormancy followed by resumed publishing is consistent with org release cadence. ai

Versions (showing 26 of 26)

Version Deps Published
14.41.1 0 / 74
14.41.0 0 / 74
14.40.0 0 / 73
14.38.0 0 / 73
14.37.3 0 / 73
14.37.2 0 / 73
14.37.1 0 / 73
14.37.0 0 / 73
14.36.0 0 / 73
14.35.1 0 / 73
14.35.0 0 / 73
14.34.1 0 / 73
14.34.0 0 / 73
14.33.0 0 / 73
14.32.0 0 / 73
14.31.0 0 / 73
14.30.0 0 / 73
14.29.2 0 / 73
14.29.1 0 / 73
14.29.0 0 / 73
14.28.0 0 / 73
14.27.1 0 / 72
14.27.0 0 / 72
14.26.1 0 / 72
14.26.0 0 / 72
14.22.2 0 / 73

v14.41.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.32.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.31.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.30.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.29.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.29.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.28.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.27.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.27.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.26.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.26.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v14.22.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.