← Home

@alpinejs/anchor

npm Repository Homepage

Anchor an element's position relative to another

23
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

calebporzio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; consistent with official alpinejs monorepo. ai

Versions (showing 23 of 23)

Version Deps Published
3.15.12 1 / 0
3.15.11 1 / 0
3.15.10 1 / 0
3.15.9 1 / 0
3.15.8 0 / 0
3.15.7 0 / 0
3.15.6 0 / 0
3.15.5 0 / 0
3.15.4 0 / 0
3.15.3 0 / 0
3.15.2 0 / 0
3.15.1 0 / 0
3.15.0 0 / 0
3.14.9 0 / 0
3.14.8 0 / 0
3.14.7 0 / 0
3.14.6 0 / 0
3.14.5 0 / 0
3.14.4 0 / 0
3.14.3 0 / 0
3.14.2 0 / 0
3.14.1 0 / 0
3.14.0 0 / 0

v3.14.9

1 finding
LOW No provenance attestation provenance

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

v3.14.8

1 finding
LOW No provenance attestation provenance

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

v3.14.7

1 finding
LOW No provenance attestation provenance

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

v3.14.6

1 finding
LOW No provenance attestation provenance

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

v3.14.5

1 finding
LOW No provenance attestation provenance

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

v3.14.4

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.

v3.14.3

1 finding
LOW No provenance attestation provenance

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

v3.14.2

1 finding
LOW No provenance attestation provenance

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

v3.14.1

1 finding
LOW No provenance attestation provenance

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

v3.14.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.