@napi-rs/canvas-android-arm64 MIT 11 versions

@napi-rs/canvas-android-arm64

npm Repository Homepage

Canvas for Node.js with skia backend

11

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

broooooklynforehalo

Keywords

napi-rsNAPIN-APIRustnode-addonnode-addon-apicanvasimagepdfsvgskia

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): This package's sole purpose is to distribute the prebuilt skia.android-arm64.node native addon. Bundled binary is expected and intentional for all versions of this platform-specific napi-rs shard.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): napi-rs/canvas uses GitHub Actions for automated publishing; the broooooklyn→GitHub Actions transition is the expected CI/CD publishing pattern for this package, confirmed by SLSA provenance attestation.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Platform-specific optional binary packages (android-arm64) legitimately have no code files, no deps, tiny payloads, and minimal READMEs — this is the standard napi-rs split-binary pattern.	ai	2026/04/23

Versions (showing 11 of 111)

Version	Deps	Published
0.0.12	0 / 0	2021-07-14
0.0.11	0 / 0	2021-07-13
0.0.10	0 / 0	2021-07-12
0.0.9	0 / 0	2021-07-11
0.0.8	0 / 0	2021-06-23
0.0.7	0 / 0	2021-06-21
0.0.6	0 / 0	2021-05-06
0.0.5	0 / 0	2021-05-04
0.0.4	0 / 0	2021-04-19
0.0.3	0 / 0	2021-03-27
0.0.2	0 / 0	2021-03-27

v0.0.12

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.

v0.0.11

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • skia.android-arm64.node

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.

v0.0.10

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.

v0.0.9

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.

v0.0.8

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.

v0.0.7

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.

v0.0.6

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.

v0.0.5

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.

v0.0.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.

v0.0.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.

v0.0.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.