← Home

balena-settings-client

npm Repository Homepage
4
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

balenasettingsclient

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established balena.io package; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:@resin.io/types-hidepath AI (phantom-deps): TypeScript type-only dep referenced in config files, not directly imported at runtime; stable pattern for this package. ai
phantom-deps phantom-dep:@resin.io/types-home-or-tmp AI (phantom-deps): TypeScript type-only dep referenced in config files, not directly imported at runtime; stable pattern for this package. ai
phantom-deps phantom-dep:@types/js-yaml AI (phantom-deps): Type declaration package loaded by convention, not direct import; stable false positive for this package. ai
dependencies unvetted-dep:hidepath AI (dependencies): hidepath is a legitimate utility used by this settings client; stable dependency across versions. ai

Versions (showing 4 of 4)

Version Deps Published
6.0.3 4 / 22
6.0.2 4 / 22
6.0.1 7 / 19
6.0.0 7 / 19

v6.0.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.

v6.0.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.

v6.0.1

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.

v6.0.0

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.