@churchapps/apphelper-donations No license 40 versions

@churchapps/apphelper-donations

npm Repository Homepage

40

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jzongkerhimali_malvawalapranavmalvawalavshal7

Keywords

ChurchAppsdonationsstripepayments

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/components/MultiGatewayDonationForm.js	AI (source-diff): Standard tsc-compiled React component output; long lines are minified JSX, not obfuscation.	ai	2026/05/13
phantom-deps	phantom-dep:rrule	AI (phantom-deps): Likely re-exported or used indirectly in a React component library; stable pattern.	ai	2026/05/07
phantom-deps	phantom-dep:date-fns	AI (phantom-deps): Likely re-exported or used indirectly in a React component library; stable pattern.	ai	2026/05/07
phantom-deps	phantom-dep:jwt-decode	AI (phantom-deps): Likely re-exported or used indirectly in a React component library; stable pattern.	ai	2026/05/07
phantom-deps	phantom-dep:axios	AI (phantom-deps): Likely re-exported or used indirectly in a React component library; stable pattern.	ai	2026/05/07
phantom-deps	phantom-dep:@emotion/react	AI (phantom-deps): Likely re-exported or used indirectly in a React component library; stable pattern.	ai	2026/05/07
phantom-deps	phantom-dep:@emotion/styled	AI (phantom-deps): Likely re-exported or used indirectly in a React component library; stable pattern.	ai	2026/05/07
phantom-deps	phantom-dep:@types/react-google-recaptcha	AI (phantom-deps): Framework-scoped type package; loaded by convention in React libraries.	ai	2026/05/07
phantom-deps	phantom-dep:react-cookie	AI (phantom-deps): Likely re-exported or used indirectly in a React component library; stable pattern.	ai	2026/05/07

Versions (showing 40 of 40)

Version	Deps	Published
0.6.22	3 / 29	2026-04-23
0.6.21	3 / 29	2026-04-09
0.6.20	3 / 29	2026-04-08
0.6.18	3 / 29	2026-03-13
0.6.17	13 / 6	2026-02-03
0.6.16	13 / 6	2026-02-02
0.6.15	13 / 6	2026-01-13
0.6.14	13 / 6	2026-01-13
0.6.13	13 / 6	2026-01-13
0.6.12	13 / 6	2026-01-12
0.6.11	13 / 6	2026-01-03
0.6.10	13 / 6	2026-01-03
0.6.9	13 / 6	2026-01-03
0.6.8	13 / 6	2026-01-03
0.6.7	13 / 6	2026-01-02
0.6.1	13 / 6	2025-12-12
0.6.0	13 / 6	2025-12-01
0.5.6	13 / 6	2025-11-04
0.5.5	13 / 6	2025-11-04
0.5.1	13 / 6	2025-10-21
0.5.0	13 / 6	2025-09-23
0.4.50	13 / 6	2025-09-17
0.4.47	13 / 6	2025-09-08
0.4.46	13 / 6	2025-09-05
0.4.45	13 / 6	2025-09-03
0.4.44	13 / 6	2025-09-03
0.4.43	11 / 6	2025-08-30
0.4.42	11 / 6	2025-08-28
0.4.41	11 / 6	2025-08-27
0.4.37	11 / 6	2025-08-27
0.4.35	11 / 6	2025-08-20
0.4.34	11 / 6	2025-08-19
0.4.33	11 / 6	2025-08-19
0.4.28	11 / 6	2025-08-07
0.4.27	12 / 6	2025-08-05
0.4.26	12 / 6	2025-07-31
0.4.25	12 / 6	2025-07-31
0.4.21	12 / 6	2025-07-25
0.4.18	12 / 6	2025-07-24
0.4.17	14 / 6	2025-07-20

v0.6.22

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.

v0.6.21

1 finding

LOW No provenance attestation provenance

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

v0.6.20

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.

v0.6.18

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.

v0.6.17

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.

v0.6.16

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.

v0.6.15

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.

v0.6.14

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.

v0.6.13

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.

v0.6.12

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.

v0.6.11

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.

v0.6.10

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.

v0.6.9

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.

v0.6.8

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.

v0.6.7

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.

v0.6.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.

v0.6.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.

v0.5.6

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.

v0.5.5

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.

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.50

1 finding

LOW No provenance attestation provenance

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

v0.4.47

2 findings

HIGH New obfuscated file: dist/components/MultiGatewayDonationForm.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.4.46

2 findings

HIGH New obfuscated file: dist/components/MultiGatewayDonationForm.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.4.45

1 finding

LOW No provenance attestation provenance

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

v0.4.44

1 finding

LOW No provenance attestation provenance

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

v0.4.43

1 finding

LOW No provenance attestation provenance

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

v0.4.42

1 finding

LOW No provenance attestation provenance

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

v0.4.41

1 finding

LOW No provenance attestation provenance

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

v0.4.37

1 finding

LOW No provenance attestation provenance

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

v0.4.35

1 finding

LOW No provenance attestation provenance

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

v0.4.34

1 finding

LOW No provenance attestation provenance

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

v0.4.33

1 finding

LOW No provenance attestation provenance

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

v0.4.28

1 finding

LOW No provenance attestation provenance

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

v0.4.27

1 finding

LOW No provenance attestation provenance

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

v0.4.26

1 finding

LOW No provenance attestation provenance

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

v0.4.25

1 finding

LOW No provenance attestation provenance

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

v0.4.21

1 finding

LOW No provenance attestation provenance

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

v0.4.18

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.

v0.4.17

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.