← Home

@websolutespa/payload-plugin-search

npm Repository Homepage

Search plugin for PayloadCms

11
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

websolute-adminactariancbrualdiamacafedericodilucagiacomo_grassettim.fortarmy75ldeblasio

Keywords

payloadsearch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): Major version rewrite from v0.x to v3.0 targeting PayloadCMS 3.x; size growth is expected. ai
source-diff source-size-tripled AI (source-diff): 4x growth consistent with major version rewrite; no obfuscation or injected payloads detected. ai
phantom-deps phantom-dep:ts-deepmerge AI (phantom-deps): ts-deepmerge is a declared runtime dependency; phantom-dep heuristic false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
3.0.1 1 / 25
3.0.0 1 / 25
2.0.0 1 / 15
0.1.2 1 / 15
0.1.1 1 / 15
0.1.0 1 / 15
0.0.5 1 / 15
0.0.4 1 / 15
0.0.3 1 / 15
0.0.2 1 / 15
0.0.1 1 / 15

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: federicodiluca → actarian (on 2024-09-20, known maintainer) provenance

This version was published by a different npm account (actarian) than the most recent previously approved version (federicodiluca) on 2024-09-20, but actarian is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: federicodiluca → actarian (on 2024-07-23, known maintainer) provenance

This version was published by a different npm account (actarian) than the most recent previously approved version (federicodiluca) on 2024-07-23, but actarian is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: federicodiluca → actarian (on 2024-05-31, known maintainer) provenance

This version was published by a different npm account (actarian) than the most recent previously approved version (federicodiluca) on 2024-05-31, but actarian is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.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.

v0.0.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.