← Home

@cap-js/cap-operator-plugin

npm Repository Homepage

Add/Build Plugin for CAP Operator

19
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

sap_extncreposcap-npmsap-ospo-admin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Transition to SAP org npm account, high approval track record. ai
maintainer-change maintainer-removed AI (maintainer-change): Same org-managed transition, no behavioral change in code. ai
semgrep semgrep:child-process-import AI (semgrep): CLI tool bin script; child_process use is expected and documented for build/deploy operations. ai

Versions (showing 19 of 19)

Version Deps Published
0.18.0 2 / 4
0.17.0 2 / 4
0.16.1 2 / 4
0.16.0 2 / 4
0.15.0 2 / 4
0.14.0 1 / 4
0.13.0 1 / 4
0.12.1 1 / 4
0.12.0 1 / 4
0.11.0 1 / 4
0.10.0 1 / 4
0.9.0 1 / 4
0.8.0 1 / 4
0.7.1 1 / 4
0.7.0 1 / 4
0.6.0 1 / 4
0.2.0 1 / 4
0.1.0 1 / 4
0.0.2 1 / 3

v0.18.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.0

2 findings
HIGH Publisher changed: chgeo → cap-npm (on 2024-08-21) provenance

This version was published by a different npm account than previous versions on 2024-08-21. This could indicate a legitimate maintainer transition or an account compromise.

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
HIGH Publisher changed: chgeo → cap-npm (on 2024-07-25) provenance

This version was published by a different npm account than previous versions on 2024-07-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

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.