← Home

@sasjs/adapter

npm Repository Homepage

JavaScript adapter for SAS

5
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

krishna-acondyallanboweyury_shkoda

Keywords

sasviyasasjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:index.js AI (source-diff): Long strings are OS constants (errno/signal/SSL) in JSON.parse — standard webpack bundle output, not malicious encoding. ai
source-diff encoded-string-file:index-dev.js AI (source-diff): Same OS constants pattern as index.js; stable bundler artifact for this package. ai
provenance no-provenance AI (provenance): Established package with 257 versions; lack of provenance is consistent across all prior releases. ai

Versions (showing 5 of 5)

Version Deps Published
4.17.0 6 / 32
4.16.7 6 / 32
4.16.6 6 / 32
4.16.5 6 / 32
4.16.4 6 / 32

v4.17.0

3 findings
HIGH Long encoded string in modified file: index-dev.js source-diff

Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: index.js source-diff

Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

INFO No provenance attestation provenance

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

v4.16.7

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

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

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

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.