@iobroker/adapter-core
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): ioBroker org migrated publishing to GitHub Actions CI with SLSA attestation; legitimate org-level change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mcm1957 is a known ioBroker org contributor; addition consistent with legitimate org maintenance. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy explained by stable mature package; SLSA attestation confirms legitimate CI publish. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.4.1 | 0 / 17 | |
| 3.3.2 | 0 / 23 | |
| 3.3.1 | 0 / 23 | |
| 3.3.0 | 0 / 23 |
v3.4.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.