← Home

@sasjs/cli

npm Repository Homepage

Command line interface for SASjs

14
Versions
ISC
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

Keywords

SASViyaSASjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established SASjs org package; lack of Sigstore attestation is a process gap, not a security risk for this package. ai
install-scripts install-script:preinstall AI (install-scripts): Preinstall only echoes a node version warning message; no network calls or code execution risk. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @sasjs/cli package with 421 versions and established org; Levenshtein match to 'joi' is a false positive. ai
phantom-deps phantom-dep:find AI (phantom-deps): find is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@sasjs/core AI (phantom-deps): Same-org dependency; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:lodash.groupby AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. ai

Versions (showing 14 of 14)

Version Deps Published
4.17.4 20 / 27
4.17.3 20 / 27
4.17.1 20 / 27
4.17.0 20 / 27
4.16.2 20 / 27
4.16.0 20 / 27
4.13.1 20 / 27
4.13.0 20 / 27
4.12.15 20 / 27
4.12.12 20 / 27
4.12.11 20 / 27
4.12.9 20 / 27
4.12.6 20 / 27
4.12.5 20 / 27

v4.17.4

1 finding
LOW No provenance attestation provenance

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

v4.17.3

1 finding
LOW No provenance attestation provenance

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

v4.17.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.

v4.17.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.

v4.16.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.

v4.16.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.

v4.13.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.

v4.13.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.

v4.12.15

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: npm run nodeVersionMessage

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.

v4.12.12

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: npm run nodeVersionMessage

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.

v4.12.11

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: npm run nodeVersionMessage

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.

v4.12.9

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: npm run nodeVersionMessage

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.

v4.12.6

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: npm run nodeVersionMessage

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.

v4.12.5

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: npm run nodeVersionMessage

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.