@sasjs/adapter
JavaScript adapter for SAS
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.17.3 | 6 / 34 | |
| 4.17.2 | 6 / 34 | |
| 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 | |
| 4.16.3 | 6 / 32 | |
| 4.16.2 | 6 / 32 | |
| 4.16.1 | 6 / 32 |
v4.17.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.17.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.
v4.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.