@signageos/sdk
Library which allows you to fully manage signageOS applets, devices, management & monitoring using JS.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/ini | AI (phantom-deps): @types/* packages are type declarations; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): @types/* packages are type declarations; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): @types/* packages are type declarations; not directly imported at runtime by convention. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 22 / 32 | |
| 2.7.0 | 22 / 32 | |
| 2.6.1 | 22 / 32 | |
| 2.6.0 | 22 / 32 | |
| 2.5.0 | 22 / 32 | |
| 2.4.1 | 22 / 32 | |
| 2.4.0 | 22 / 32 | |
| 2.3.0 | 22 / 32 | |
| 2.2.0 | 22 / 32 | |
| 2.1.1 | 22 / 32 | |
| 2.1.0 | 22 / 32 | |
| 2.0.3 | 22 / 32 | |
| 2.0.2 | 22 / 32 | |
| 2.0.1 | 22 / 32 |
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.