← Home

chargebee

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

chargebee_ui

Keywords

paymentsbillingssubscriptionchargebee

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Loads local schema files by name from a fixed subdirectory; not user-controlled arbitrary module loading. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is used for Basic Auth header parsing in webhook authentication — standard, benign pattern for this SDK. ai

Versions (showing 41 of 41)

Version Deps Published
3.28.1 1 / 10
3.28.0 1 / 10
3.27.0 1 / 9
3.26.0 0 / 9
3.25.0 0 / 9
3.24.1 0 / 9
3.24.0 0 / 9
3.23.1 0 / 9
3.23.0 0 / 9
3.22.1 0 / 9
3.22.0 0 / 9
3.21.1 0 / 9
3.21.0 0 / 9
3.20.0 0 / 3
3.19.0 0 / 3
3.18.0 0 / 3
3.17.0 0 / 3
3.16.2 0 / 3
3.16.1 0 / 3
3.16.0 0 / 3
3.15.1 0 / 3
3.15.0 0 / 3
3.14.0 0 / 3
3.13.0 0 / 3
3.12.0 0 / 3
3.11.0 0 / 3
3.10.0 0 / 3
3.9.0 0 / 3
3.8.0 0 / 3
3.7.0 0 / 3
3.6.1 0 / 3
3.6.0 0 / 3
3.5.0 0 / 3
3.4.0 0 / 3
3.3.0 0 / 3
3.2.1 0 / 3
3.2.0 0 / 3
3.1.0 0 / 3
3.0.2 0 / 3
3.0.1 0 / 3
3.0.0 0 / 3

v3.28.1

1 finding
LOW No provenance attestation provenance

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

v3.28.0

1 finding
LOW No provenance attestation provenance

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

v3.27.0

1 finding
LOW No provenance attestation provenance

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

v3.6.1

1 finding
LOW No provenance attestation provenance

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

v3.6.0

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

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