@propellerads/kyc-form
`KycForm`.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@propellerads/textarea | AI (dependencies): Internal propellerads org component; consistent with the package's established dependency pattern. | ai | |
| dependencies | unvetted-dep:@propellerads/success-label | AI (dependencies): Internal propellerads org component; consistent with the package's established dependency pattern. | ai | |
| dependencies | unvetted-dep:@propellerads/image-uploader | AI (dependencies): Internal propellerads org component; consistent with the package's established dependency pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 6 / 6 | |
| 4.1.8 | 6 / 5 | |
| 4.1.7 | 6 / 5 | |
| 4.1.6 | 6 / 5 | |
| 4.1.5 | 6 / 5 | |
| 4.1.4 | 6 / 5 | |
| 4.1.3 | 6 / 5 | |
| 4.1.2 | 6 / 5 | |
| 4.1.1 | 6 / 5 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.