@cap-js/asyncapi
4
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
CAPCDSAsyncAPINode.js
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA provenance; consistent with SAP org automation migration. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin addition aligns with SAP open-source org governance; not a suspicious third-party. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads project's own package.json via cds.root path join; not user-controlled, stable false positive for this package. | ai |
v1.0.2
2 findings
MEDIUM
Publisher changed: chgeo → cap-npm (on 2024-07-15, unremoved on npm for 733d)
provenance
This version was published by a different npm account (cap-npm) than the most recent previously approved version (chgeo) on 2024-07-15. It has since remained available on npm for 733 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.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.