← Home

@sassoftware/restaflib

npm Repository Homepage

collection of useful functions for common scenarios

16
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

coalmanjefurbeedevakumaraswamyckedwardsrbtleveybrmorrbjtomlinjolynamtlsmcmtlstgryanauldsaskenjacksonmtlhmomartin-coutts-sasromacftimothy.crider-sasdaarthewsken_sasmtlcmcmtlnshtom-mceachan_sasinst

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:eval-usage AI (semgrep): All eval() calls are webpack bundle runtime artifacts in the built lib/restaflib.js; stable false positive for this package. ai
provenance no-provenance AI (provenance): Established SAS org package; lack of Sigstore provenance is common and not a risk signal here. ai

Versions (showing 16 of 16)

Version Deps Published
5.7.2 0 / 0
5.7.1 0 / 0
5.7.0 0 / 0
5.6.0 0 / 0
2.14.0 2 / 0
2.13.27 2 / 0
2.13.26 2 / 0
2.13.25 2 / 0
2.13.23 2 / 0
2.13.22 2 / 0
2.13.21 2 / 0
2.13.20 2 / 0
2.13.19 2 / 0
2.13.18 2 / 0
2.3.11 2 / 0
2.3.10 2 / 0

v2.14.0

1 finding
INFO No provenance attestation provenance

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

v2.13.27

1 finding
INFO No provenance attestation provenance

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

v2.13.26

1 finding
INFO No provenance attestation provenance

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

v2.13.25

1 finding
INFO No provenance attestation provenance

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

v2.13.23

1 finding
INFO No provenance attestation provenance

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

v2.13.22

1 finding
INFO No provenance attestation provenance

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

v2.13.21

1 finding
INFO No provenance attestation provenance

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

v2.13.20

1 finding
INFO No provenance attestation provenance

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

v2.13.19

1 finding
INFO No provenance attestation provenance

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

v2.13.18

1 finding
INFO No provenance attestation provenance

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

v2.3.11

1 finding
INFO No provenance attestation provenance

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