← Home

balena-sdk

npm Repository Homepage
12
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

balena.io

Keywords

sdkresinresin.iobalenabalena.ioiotdevices

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Balena-io org migrated publishing to GitHub Actions with SLSA attestation; expected CI/CD transition for this package. ai
publish-pattern rapid-publish AI (publish-pattern): Automated CI/CD pipeline with SLSA provenance; rapid publishes are expected for this package. ai
dependencies unvetted-dep:handlebars AI (dependencies): Handlebars is a well-known templating library; stable long-term dependency of this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Pattern is a documented ES-version selector loading a known local build path; stable across versions. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Type-only package; not imported at runtime by convention. ai
phantom-deps phantom-dep:@types/json-schema AI (phantom-deps): Type-only package; not imported at runtime by convention. ai

Versions (showing 12 of 12)

Version Deps Published
23.2.3 18 / 47
23.2.2 18 / 47
23.1.18 18 / 47
23.1.6 18 / 48
23.1.5 18 / 48
23.0.4 20 / 47
23.0.2 20 / 47
22.4.9 21 / 46
22.4.5 21 / 46
22.4.4 21 / 46
22.4.3 21 / 49
22.4.2 21 / 49

v23.2.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v23.2.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v23.1.18

2 findings
HIGH Publisher changed: balena.io → GitHub Actions (on 2026-04-21) provenance

This version was published by a different npm account than previous versions on 2026-04-21. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v23.1.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v23.1.5

2 findings
HIGH Publisher changed: balena.io → GitHub Actions (on 2026-03-11) provenance

This version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v23.0.4

2 findings
HIGH Publisher changed: balena.io → GitHub Actions (on 2026-02-26) provenance

This version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v23.0.2

2 findings
HIGH Publisher changed: balena.io → GitHub Actions (on 2026-02-13) provenance

This version was published by a different npm account than previous versions on 2026-02-13. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v22.4.9

2 findings
HIGH Publisher changed: balena.io → GitHub Actions (on 2026-02-03) provenance

This version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v22.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v22.4.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v22.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.