@churchapps/apphelper-forms
Form components for ChurchApps AppHelper - general forms without payment processing
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Re-exported utility dep in a component library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Re-exported utility dep in a component library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): MUI peer/transitive dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): MUI peer/transitive dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@churchapps/apphelper-donations | AI (phantom-deps): Same-org monorepo dependency; declared as runtime dep, likely re-exported rather than directly imported. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.6.16 | 1 / 26 | |
| 0.6.15 | 1 / 26 | |
| 0.6.14 | 7 / 6 | |
| 0.6.11 | 7 / 6 | |
| 0.6.10 | 7 / 6 | |
| 0.6.9 | 7 / 6 | |
| 0.6.8 | 7 / 6 | |
| 0.6.7 | 7 / 6 | |
| 0.6.0 | 7 / 6 | |
| 0.5.6 | 7 / 6 | |
| 0.5.5 | 7 / 6 | |
| 0.5.0 | 7 / 6 | |
| 0.4.50 | 7 / 6 | |
| 0.4.47 | 7 / 6 | |
| 0.4.46 | 7 / 6 | |
| 0.4.44 | 7 / 6 | |
| 0.4.41 | 7 / 6 | |
| 0.4.37 | 7 / 6 | |
| 0.4.35 | 7 / 6 | |
| 0.4.34 | 7 / 6 | |
| 0.4.33 | 7 / 6 | |
| 0.4.30 | 7 / 6 | |
| 0.4.29 | 7 / 6 | |
| 0.4.28 | 7 / 6 | |
| 0.4.27 | 8 / 6 |
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.