← Home

@sasjs/utils

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

krishna-acondyallanboweyury_shkoda

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Preinstall only echoes a node version reminder via npm run nodeVersionMessage; no network or exec risk. ai
semgrep semgrep:base64-decode AI (semgrep): Legitimate password-decoding utility with SASjs-specific prefix check; no exfiltration or obfuscation. ai
phantom-deps phantom-dep:@types/prompts AI (phantom-deps): @types packages are type-only and loaded by convention; stable false positive for this package. ai
phantom-deps phantom-dep:@types/fs-extra AI (phantom-deps): @types packages are type-only and loaded by convention; stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
3.5.9 11 / 15
3.5.8 11 / 12
3.5.7 11 / 12
3.5.6 11 / 12
3.5.4 11 / 12
3.5.3 11 / 12

v3.5.9

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: allanbowe → GitHub Actions (on 2026-07-21, 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 (allanbowe) on 2026-07-21, 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.