@things-factory/operato-board
App for dashboarding
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package; provenance not historically used in this ecosystem. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 in a development config file — not a malicious exfiltration endpoint. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in migration index loader is a standard pattern for this framework; not arbitrary code loading. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 9.2.25 | 80 / 2 | |
| 8.0.87 | 78 / 2 | |
| 6.4.11 | 73 / 2 | |
| 6.4.10 | 73 / 2 | |
| 4.3.822 | 62 / 2 | |
| 4.3.815 | 62 / 2 | |
| 4.3.791 | 62 / 2 | |
| 4.3.790 | 62 / 2 | |
| 4.3.740 | 62 / 2 | |
| 4.3.652 | 62 / 2 |
v9.2.25
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nalshya113) than the most recent previously approved version (horwengliang95) on 2026-06-08, but nalshya113 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.
v8.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.815
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.791
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.790
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.740
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.652
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.