@signageos/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @signageos/core; Levenshtein match to 'cors' is incidental, not a typosquat. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.8.0 | 0 / 11 | |
| 1.7.0 | 0 / 10 | |
| 1.6.0 | 0 / 10 | |
| 1.5.0 | 0 / 10 | |
| 1.4.0 | 0 / 10 | |
| 1.3.0 | 0 / 10 | |
| 1.2.1 | 0 / 10 | |
| 1.2.0 | 0 / 10 | |
| 1.1.1 | 0 / 10 | |
| 1.1.0 | 0 / 10 | |
| 1.0.0 | 0 / 10 |
v1.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (misak113) than the most recent previously approved version (signageos.io) on 2026-07-07, but misak113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.