@msgpackr-extract/msgpackr-extract-win32-x64 MIT 11 versions

@msgpackr-extract/msgpackr-extract-win32-x64

npm Repository Homepage

Platform specific binary for msgpackr-extract on win32 OS with x64 architecture

11

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kriszyp

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): Platform-specific native addon package by canonical msgpackr author; .node binaries are the expected deliverable for this os/cpu-scoped package.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Minimal metadata (no README code, no keywords, no deps, empty index.js) is the standard pattern for platform-specific binary sub-packages; not indicative of spam or malice.	ai	2026/04/23

Versions (showing 11 of 11)

Version	Deps	Published
3.0.4	0 / 0	2026-05-25
3.0.3	0 / 0	2024-06-09
3.0.2	0 / 0	2023-03-01
3.0.1	0 / 0	2023-02-27
3.0.0	0 / 0	2023-01-31
2.2.0	0 / 0	2022-11-12
2.1.2	0 / 0	2022-08-01
2.1.1	0 / 0	2022-08-01
2.1.0	0 / 0	2022-07-30
2.0.2	0 / 0	2022-05-18
2.0.0	0 / 0	2022-05-18

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • node.abi115.node • node.napi.node

LOW No provenance attestation provenance

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

v3.0.2

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • node.abi108.node • node.napi.node

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

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