@signalk/freeboard-sk
Openlayers chart plotter implementation for Signal K
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:public/main-YHMZXR5G.js | AI (source-diff): Angular production build output; minified bundles with hashed names are expected for this package. | ai | |
| source-diff | obfuscated-file:public/worker-V6HMSEDU.js | AI (source-diff): Angular production build worker bundle; minification is expected for this package. | ai | |
| source-diff | net-exec-file:public/chunk-AZK5ODAA.js | AI (source-diff): Bundled Worker + async generator polyfill in Angular build output; not a dropper pattern for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires in Angular production bundle; standard build artifact pattern, not a payload. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): Eval in worker bundle is Google Closure Compiler's dependency loader pattern, not malicious. | ai | |
| phantom-deps | phantom-dep:google-protobuf | AI (phantom-deps): google-protobuf is a runtime dep used via generated protobuf code; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.23.0 | 5 / 50 | |
| 2.22.1 | 5 / 48 | |
| 2.22.0 | 5 / 48 | |
| 2.21.0 | 5 / 48 |
v2.23.0
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.