← Home

@keeper-security/secrets-manager-core

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

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

saldoukhov-keepersec_managertheflinkeepertyleratkeeper

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Standard base64 utility in a secrets manager SDK; not a payload-hiding pattern. ai

Versions (showing 6 of 6)

Version Deps Published
17.5.0 0 / 15
17.4.0 0 / 15
17.3.0 0 / 15
17.2.0 0 / 14
17.1.0 0 / 14
17.0.0 0 / 14

v17.5.0

2 findings
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.

INFO Publisher changed: sec_manager → GitHub Actions (on 2026-07-01, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (sec_manager) on 2026-07-01, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

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