@napi-rs/canvas-darwin-x64 MIT 11 versions

@napi-rs/canvas-darwin-x64

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 ship the precompiled skia.darwin-x64.node binary for the napi-rs canvas library. Bundled binary is expected and intentional for this platform-specific distribution pattern.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher changed from broooooklyn to GitHub Actions as part of a legitimate CI/CD migration; confirmed by SLSA provenance attestation linking back to the canonical Brooooooklyn/canvas repo.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Platform-specific napi-rs binary sub-packages legitimately have no code files, no deps, and minimal READMEs — the payload is a single prebuilt .node binary.	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

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