← Home

@unisat/preference-service

npm

Cross-platform preference management service for UniSat wallet

9
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

huanniangstudio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@unisat/i18n AI (dependencies): Same @unisat org namespace; consistent with internal package family, not a third-party supply-chain risk. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are same-org @unisat scoped packages, consistent with normal monorepo expansion. ai
phantom-deps phantom-dep:debounce AI (phantom-deps): debounce is a declared runtime dependency; phantom-dep heuristic misfired on this package's import pattern. ai

Versions (showing 9 of 9)

Version Deps Published
0.3.0 6 / 7
0.2.0 6 / 7
0.1.6 6 / 7
0.1.5 6 / 7
0.1.4 5 / 7
0.1.3 5 / 7
0.1.2 5 / 6
0.1.1 3 / 6
0.1.0 3 / 6

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.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.

v0.1.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.