← Home

@akinon/akiform-builder

Form builder library for form operations.

16
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

akinon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@akinon/akidate AI (dependencies): Sibling package from same Akinon publisher with consistent track record; stable false positive for this ecosystem. ai
provenance no-provenance AI (provenance): Akinon org packages consistently lack provenance; stable false positive for this publisher. ai

Versions (showing 16 of 16)

Version Deps Published
1.6.2 17 / 8
1.6.1 17 / 8
1.6.0 17 / 8
1.5.11 17 / 8
1.5.9 17 / 8
1.5.7 17 / 8
1.5.6 17 / 8
1.5.5 17 / 8
1.5.2 17 / 8
1.5.1 17 / 8
1.5.0 17 / 8
1.4.0 17 / 8
1.3.4 17 / 8
1.3.2 16 / 7
1.0.1 16 / 6
1.0.0 13 / 6

v1.6.2

1 finding
INFO No provenance attestation provenance

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

v1.6.1

1 finding
INFO No provenance attestation provenance

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

v1.6.0

1 finding
INFO No provenance attestation provenance

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

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.