← Home

@cap-js/openapi

npm Repository Homepage
17
Versions
—
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

Keywords

CAPCDSOpenAPINode.js

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Org-level maintainer transition to trusted cap-npm publisher, stable for 718d. ai
maintainer-change maintainer-removed AI (maintainer-change): Expected consequence of same org transfer, not a takeover. ai
provenance publisher-changed-stale AI (provenance): Stale, long-unremoved publisher change; not indicative of compromise. ai
semgrep semgrep:dynamic-require AI (semgrep): Config-file loader pattern guarded by existsSync; user controls the path intentionally as a CLI option. ai

Versions (showing 17 of 17)

Version Deps Published
1.5.0 1 / 5
1.4.2 1 / 4
1.4.0 1 / 4
1.3.1 1 / 4
1.3.0 1 / 4
1.2.3 1 / 2
1.2.2 1 / 2
1.2.1 1 / 2
1.2.0 1 / 2
1.1.2 1 / 2
1.1.1 1 / 2
1.1.0 1 / 2
1.0.7 1 / 2
1.0.6 1 / 2
1.0.5 1 / 2
1.0.4 1 / 2
1.0.3 1 / 2

v1.2.1

2 findings
MEDIUM Publisher changed: chgeo → cap-npm (on 2025-03-12, unremoved on npm for 493d) provenance

This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2025-03-12. It has since remained available on npm for 493 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.2.0

2 findings
MEDIUM Publisher changed: chgeo → cap-npm (on 2025-02-28, unremoved on npm for 505d) provenance

This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2025-02-28. It has since remained available on npm for 505 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.1.2

2 findings
MEDIUM Publisher changed: chgeo → cap-npm (on 2025-01-27, unremoved on npm for 537d) provenance

This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2025-01-27. It has since remained available on npm for 537 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.1.1

2 findings
MEDIUM Publisher changed: chgeo → cap-npm (on 2024-12-13, unremoved on npm for 582d) provenance

This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2024-12-13. It has since remained available on npm for 582 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.1.0

2 findings
MEDIUM Publisher changed: chgeo → cap-npm (on 2024-12-04, unremoved on npm for 591d) provenance

This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2024-12-04. It has since remained available on npm for 591 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.7

2 findings
MEDIUM Publisher changed: chgeo → cap-npm (on 2024-10-17, unremoved on npm for 639d) provenance

This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2024-10-17. It has since remained available on npm for 639 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.6

2 findings
MEDIUM Publisher changed: chgeo → cap-npm (on 2024-09-23, unremoved on npm for 663d) provenance

This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2024-09-23. It has since remained available on npm for 663 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.5

2 findings
MEDIUM Publisher changed: chgeo → cap-npm (on 2024-07-30, unremoved on npm for 718d) provenance

This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2024-07-30. It has since remained available on npm for 718 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.4

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

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.