@signageos/front-display
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.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 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.29.2 | 0 / 73 |
v14.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.37.3
2 findingsModified file contains 9 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.37.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.37.1
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.37.0
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.36.0
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.35.1
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.35.0
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.34.1
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.34.0
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.