← Home

@formulajs/formulajs

npm Repository Homepage
30
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

Verified SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

nicolashefti

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:eval-usage AI (semgrep): eval() is in bin/cli.js to evaluate user-supplied formula expressions at the command line — a legitimate REPL pattern with no supply-chain attack surface. ai

Versions (showing 30 of 30)

Version Deps Published
4.6.1 2 / 16
4.6.0 2 / 16
4.5.6 2 / 16
4.5.5 2 / 16
4.5.4 2 / 16
4.5.3 2 / 16
4.5.2 2 / 16
4.5.1 2 / 17
4.5.0 2 / 17
4.4.11 2 / 16
4.4.10 2 / 16
4.4.9 2 / 16
4.4.8 2 / 16
4.4.7 2 / 16
4.4.6 2 / 16
4.4.5 2 / 16
4.4.4 2 / 16
4.4.3 2 / 16
4.4.2 2 / 15
4.4.1 2 / 15
4.4.0 2 / 15
4.3.4 2 / 15
4.3.3 2 / 15
4.3.2 2 / 15
4.3.1 2 / 15
4.3.0 2 / 15
4.2.1 2 / 15
4.2.0 2 / 15
4.1.0 2 / 15
4.0.0 2 / 15

v4.6.1

1 finding
INFO Has verified SLSA provenance attestation provenance

Published via CI/CD with a Sigstore attestation that VERIFIED against the pinned Sigstore trust root (predicate: https://slsa.dev/provenance/v1, issuer: https://token.actions.githubusercontent.com). The attestation's sha512 subject digest matches the tarball bytes we streamed, so it describes this exact artifact. This is the strongest supply chain integrity signal.

v4.4.11

1 finding
LOW No provenance attestation provenance

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

v4.4.10

1 finding
LOW No provenance attestation provenance

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

v4.4.8

1 finding
LOW No provenance attestation provenance

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

v4.4.7

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v4.4.3

1 finding
LOW No provenance attestation provenance

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

v4.4.2

1 finding
LOW No provenance attestation provenance

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

v4.4.1

1 finding
LOW No provenance attestation provenance

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

v4.4.0

1 finding
LOW No provenance attestation provenance

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

v4.3.4

1 finding
LOW No provenance attestation provenance

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

v4.3.3

1 finding
LOW No provenance attestation provenance

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

v4.3.2

1 finding
LOW No provenance attestation provenance

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

v4.3.1

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.1

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.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.0.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.