← Home

@xrplf/secret-numbers

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

bmollintransiashichengripple001vjkhannarippleripplex-automation

Keywords

xrpxrpl-ledgermulti signsign

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance slsa-provenance AI (provenance): SLSA attestation confirms CI/CD publish from the official XRPLF GitHub org. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI/CD publish is expected for this org. ai
provenance missing-githead AI (provenance): GitHub Actions publish flow omits gitHead; SLSA provenance compensates. ai

Versions (showing 2 of 2)

Version Deps Published
3.0.0 2 / 0
2.0.0 2 / 0

v3.0.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: ckeshavabs → GitHub Actions (on 2026-06-05) provenance

This version was published by a different npm account than previous versions on 2026-06-05. 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.

v2.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.