← Home

node-aes-gcm

npm Repository Homepage

AES GCM module for node.js that takes advantage of GCM authentication

5
Versions
MIT
License
Yes
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

xorbit

Keywords

AESGCMauthentication tagGalois Counter Modeadditional authenticated dataAAD

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:install AI (install-scripts): node-gyp rebuild is the standard install script for native Node.js addons; stable and expected for this package. ai
npm-metadata bundled-binaries AI (npm-metadata): Compiled .node and .o artifacts are the expected output of node-gyp rebuild for this native AES-GCM binding; consistent across all versions. ai
phantom-deps phantom-dep:nan AI (phantom-deps): nan is used in native addon build config (binding.gyp), not imported in JS; this is standard usage for NAN-based native addons. ai

Versions (showing 5 of 5)

Version Deps Published
0.2.6 1 / 2
0.1.8 1 / 3
0.1.6 1 / 3
0.1.2 0 / 0
0.1.0 0 / 0

v0.2.6

3 findings
HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • build/Release/node_aes_gcm.node • build/Release/obj.target/node_aes_gcm/src/node-aes-gcm.o

LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xorbit.

LOW No provenance attestation provenance

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

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