← Home

@nativescript/canvas-babylon

npm Repository Homepage

```javascript ns plugin add @nativescript/canvas-babylon ```

36
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rigor789nativescript-bot

Keywords

NativeScriptJavaScriptTypeScriptiOSAndroid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:babylonjs AI (phantom-deps): babylonjs is a declared peer dep for this canvas-babylon integration; not directly imported in plugin code by design. ai

Versions (showing 36 of 36)

Version Deps Published
2.1.17 2 / 0
2.1.16 2 / 0
2.1.15 2 / 0
2.1.13 2 / 0
2.1.12 2 / 0
2.1.11 2 / 0
2.1.10 2 / 0
2.1.7 2 / 0
2.1.2 2 / 0
2.1.1 2 / 0
2.1.0 2 / 0
2.0.32 2 / 0
2.0.31 2 / 0
2.0.30 2 / 0
2.0.29 2 / 0
2.0.28 2 / 0
2.0.27 2 / 0
2.0.26 2 / 0
2.0.25 2 / 0
2.0.24 2 / 0
2.0.23 2 / 0
2.0.22 2 / 0
2.0.20 2 / 0
2.0.18 2 / 0
2.0.16 2 / 0
2.0.14 2 / 0
2.0.12 2 / 0
2.0.11 2 / 0
2.0.8 2 / 0
2.0.7 2 / 0
2.0.6 2 / 0
2.0.4 2 / 0
2.0.3 2 / 0
2.0.2 2 / 0
2.0.1 2 / 0
2.0.0 2 / 0

v2.1.17

1 finding
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.

v2.1.16

1 finding
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.

v2.1.15

1 finding
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.

v2.1.13

1 finding
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.

v2.1.12

1 finding
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.

v2.1.11

1 finding
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.

v2.1.10

1 finding
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.

v2.1.7

2 findings
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.

INFO Publisher changed: nativescript-bot → GitHub Actions (on 2026-07-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (nativescript-bot) on 2026-07-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.0.32

1 finding
LOW No provenance attestation provenance

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

v2.0.31

1 finding
LOW No provenance attestation provenance

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

v2.0.30

1 finding
LOW No provenance attestation provenance

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