@n3oltd/donation-form
A N3O Package for use in client websites.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@n3oltd/umbraco-giving-client | AI (dependencies): First-party @n3oltd scoped dep; consistent with publisher's own ecosystem across versions. | ai | |
| dependencies | unvetted-dep:@n3oltd/umbraco-giving-cart-client | AI (dependencies): First-party @n3oltd scoped dep; consistent with publisher's own ecosystem across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; no provenance is consistent across all 62 versions and is not a risk indicator here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.0.48 | 5 / 18 | |
| 1.0.47 | 5 / 18 | |
| 1.0.46 | 5 / 18 | |
| 1.0.45 | 5 / 18 | |
| 1.0.44 | 5 / 18 | |
| 1.0.43 | 5 / 18 | |
| 1.0.42 | 5 / 18 | |
| 1.0.41 | 5 / 18 | |
| 1.0.40 | 5 / 18 | |
| 1.0.39 | 5 / 18 | |
| 1.0.38 | 5 / 18 | |
| 1.0.37 | 5 / 18 | |
| 1.0.36 | 5 / 18 | |
| 1.0.35 | 5 / 18 | |
| 1.0.33 | 5 / 18 | |
| 1.0.32 | 5 / 18 | |
| 1.0.31 | 5 / 18 | |
| 1.0.30 | 5 / 18 | |
| 1.0.29 | 5 / 18 | |
| 1.0.28 | 5 / 18 | |
| 1.0.27 | 5 / 18 |
v1.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.