← Home

alpinejs

npm Repository Homepage

The rugged, minimal JavaScript framework

13
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
source-diff net-exec-file:dist/module.esm.min.js AI (source-diff): Minified framework bundle; network+exec patterns are core Alpine.js functionality. ai
publish-pattern dormant-publish AI (publish-pattern): Established package with SLSA provenance; infrequent releases are normal. ai
semgrep semgrep:new-function-constructor AI (semgrep): Alpine.js is a template/expression engine; new Function() is its core expression evaluation mechanism — intentional, documented, and not a supply-chain risk. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() is used in Alpine's Proxy-based scope/reactivity system — standard idiomatic JavaScript, not obfuscation. ai

Versions (showing 13 of 13)

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 1 / 0
3.15.7 1 / 0
3.15.6 1 / 0
3.15.5 1 / 0
3.15.4 1 / 0
3.15.3 1 / 0
3.15.2 1 / 0
3.15.1 1 / 0
3.15.0 1 / 0

v3.15.12

2 findings
HIGH New file with network + code execution: dist/module.esm.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.15.10

1 finding
LOW No provenance attestation provenance

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

v3.15.9

1 finding
LOW No provenance attestation provenance

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

v3.15.8

1 finding
LOW No provenance attestation provenance

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

v3.15.7

1 finding
LOW No provenance attestation provenance

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

v3.15.6

1 finding
LOW No provenance attestation provenance

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

v3.15.5

1 finding
LOW No provenance attestation provenance

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

v3.15.4

1 finding
LOW No provenance attestation provenance

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

v3.15.3

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.15.2

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.15.1

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.15.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.