← Home

@sassoftware/restafedit

npm Repository Homepage

Library for data editing in SAS Viya

10
Versions
Apache-2.0
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

coalmanjefurbeedevakumaraswamyckedwardsrbtleveybrmorrbjtomlinjolynamtlsmcmtlstgryanauldsaskenjacksonmtlhmomartin-coutts-sasromacftimothy.crider-sasdaarthewsken_sasmtlcmcmtlnshtom-mceachan_sasinst

Keywords

SASViyaEditingrestafrestafedit

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@sassoftware/restaf AI (phantom-deps): Same-org dep consumed via webpack bundle; not directly imported in source but legitimately declared. ai
phantom-deps phantom-dep:@sassoftware/restaflib AI (phantom-deps): Same-org dep consumed via webpack bundle; not directly imported in source but legitimately declared. ai
semgrep semgrep:eval-usage AI (semgrep): All eval() calls are webpack harmony-export boilerplate, not dynamic user input. Stable pattern for this webpack-bundled package. ai

Versions (showing 10 of 10)

Version Deps Published
3.10.5 4 / 15
3.10.4 4 / 15
3.10.3 2 / 15
3.10.2 2 / 42
3.10.0 2 / 42
3.9.0 2 / 42
3.8.2 2 / 42
3.8.1 2 / 42
3.8.0 2 / 42
3.6.3 2 / 42

v3.10.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.

v3.10.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.

v3.10.3

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.

v3.10.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.

v3.10.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.

v3.9.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.

v3.8.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.

v3.8.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.

v3.8.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.

v3.6.3

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.