@edirect/encrypt-modules
Encrypt Modules
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:archiver-zip-encrypted | AI (phantom-deps): Referenced in NX config; monorepo build pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nestjs/common | AI (phantom-deps): Referenced in NX config; monorepo build pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:stream-buffers | AI (phantom-deps): Referenced in NX config; monorepo build pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:openpgp | AI (phantom-deps): Referenced in NX config; monorepo build pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:archiver | AI (phantom-deps): Referenced in NX config; monorepo build pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:node-rsa | AI (phantom-deps): Referenced in NX config; monorepo build pattern, not a real phantom dep. | ai | |
| dependencies | unvetted-dep:stream-buffers | AI (dependencies): stream-buffers is a well-known, stable npm utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established scoped package; lack of provenance is consistent across all 37 versions and is not a risk indicator here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 11.0.56 | 7 / 5 | |
| 11.0.55 | 7 / 5 | |
| 11.0.54 | 7 / 5 | |
| 11.0.53 | 7 / 5 | |
| 11.0.50 | 7 / 5 | |
| 11.0.47 | 7 / 5 | |
| 11.0.45 | 7 / 5 | |
| 11.0.36 | 7 / 5 | |
| 11.0.33 | 7 / 5 | |
| 11.0.32 | 7 / 5 | |
| 11.0.31 | 7 / 5 | |
| 11.0.30 | 7 / 5 | |
| 11.0.29 | 7 / 5 |
v11.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.