@msgpackr-extract/msgpackr-extract-linux-arm MIT 10 versions

@msgpackr-extract/msgpackr-extract-linux-arm

npm Repository Homepage

Platform specific binary for msgpackr-extract on linux OS with arm architecture

10

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): This package's sole purpose is shipping prebuilt .node native binaries for Linux ARM. Bundled binaries are expected and intentional for this platform-specific package.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Platform-specific binary packages structurally lack deps, keywords, code in README, and have empty index.js — these are expected characteristics, not spam signals.	ai	2026/04/23

Versions (showing 10 of 10)

Version	Deps	Published
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.3

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • node.abi115.musl.node • node.napi.musl.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 (4) npm-metadata

Package contains compiled binaries that could be backdoors: • node.abi108.glibc.node • node.abi108.musl.node • node.napi.glibc.node • node.napi.musl.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.