← Home

@saltcorn/plugins-loader

npm Repository Homepage

Saltcorn plugin loader

27
Versions
MIT
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

tanielsenchristianhugoch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Passing process.env to a child npm install process is standard; no exfiltration path. ai
semgrep semgrep:child-process-import AI (semgrep): Plugin loader legitimately uses child_process to run npm install; expected for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is the core mechanism for loading installed plugins; stable pattern for this package. ai

Versions (showing 27 of 27)

Version Deps Published
1.6.1 5 / 0
1.6.0 5 / 0
1.5.8 4 / 0
1.5.7 4 / 0
1.5.6 4 / 0
1.5.5 4 / 0
1.5.4 4 / 0
1.5.3 4 / 0
1.5.2 4 / 0
1.5.1 4 / 0
1.5.0 4 / 0
1.4.6 4 / 0
1.4.5 4 / 0
1.4.4 4 / 0
1.4.3 4 / 0
1.4.2 4 / 0
1.4.1 4 / 0
1.4.0 4 / 0
1.3.1 4 / 0
1.3.0 4 / 0
1.2.0 4 / 0
1.1.4 4 / 0
1.1.3 4 / 0
1.1.2 4 / 0
1.1.1 4 / 0
1.1.0 4 / 0
1.0.0 3 / 0

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

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