← Home

@cap-js/ord

npm Repository Homepage

CAP Plugin for generating ORD document.

33
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
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; expected for SAP/cap-js org. ai
maintainer-change maintainer-added AI (maintainer-change): sap-ospo-admin is SAP's OSS admin account; consistent with org governance, not a takeover. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped SAP package @cap-js/ord; Levenshtein match to 'cors' is a false positive. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped SAP package @cap-js/ord; Levenshtein match to 'zod' is a false positive. ai
semgrep semgrep:base64-decode AI (semgrep): Standard Basic Auth header decoding pattern; not obfuscation or payload hiding. ai
semgrep semgrep:dynamic-require AI (semgrep): Loads sibling @cap-js plugin modules by name from a controlled PROTOCOL_PROVIDERS map; not arbitrary code loading. ai

Versions (showing 33 of 33)

Version Deps Published
1.9.1 6 / 10
1.9.0 6 / 10
1.8.0 6 / 8
1.7.0 6 / 8
1.6.0 6 / 8
1.5.0 6 / 8
1.4.5 5 / 8
1.4.4 5 / 7
1.4.3 5 / 7
1.4.2 5 / 7
1.4.1 5 / 7
1.4.0 5 / 6
1.3.14 5 / 4
1.3.13 5 / 4
1.3.12 5 / 3
1.3.11 5 / 3
1.3.10 5 / 3
1.3.9 5 / 3
1.3.8 5 / 3
1.3.7 5 / 3
1.3.6 5 / 3
1.3.5 4 / 3
1.3.4 4 / 3
1.3.3 4 / 3
1.3.2 4 / 3
1.3.1 4 / 3
1.3.0 4 / 3
1.2.0 1 / 2
1.1.0 1 / 2
1.0.3 0 / 1
1.0.2 0 / 1
1.0.1 0 / 1
1.0.0 0 / 1

v1.9.1

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.

v1.2.0

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.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: chgeo → cap-npm (on 2024-08-02) provenance

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

v1.0.2

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

[Accepted risk] 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.

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

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.