@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, so a manually published version cannot be tied back to a reviewed commit.
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 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 11.0.61 | 7 / 4 | |
| 11.0.56 | 7 / 5 | |
| 11.0.55 | 7 / 5 | |
| 11.0.54 | 7 / 5 | |
| 11.0.53 | 7 / 5 | |
| 11.0.51 | 7 / 5 | |
| 11.0.50 | 7 / 5 | |
| 11.0.49 | 7 / 5 | |
| 11.0.48 | 7 / 5 | |
| 11.0.47 | 7 / 5 | |
| 11.0.46 | 7 / 5 | |
| 11.0.45 | 7 / 5 | |
| 11.0.44 | 7 / 5 | |
| 11.0.43 | 7 / 5 | |
| 11.0.42 | 7 / 5 | |
| 11.0.41 | 7 / 5 | |
| 11.0.40 | 7 / 5 | |
| 11.0.39 | 7 / 5 | |
| 11.0.38 | 7 / 5 | |
| 11.0.37 | 7 / 5 | |
| 11.0.36 | 7 / 5 | |
| 11.0.35 | 7 / 5 | |
| 11.0.34 | 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 | |
| 11.0.26 | 7 / 5 |
v11.0.61
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (iquirino.bolttech) than the most recent previously approved version (matheus.maciel.bolttech) on 2026-07-13, but iquirino.bolttech is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.0.51
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: matheus.maciel.bolttech.
This version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.49
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (iquirino.bolttech) than the most recent previously approved version (diogopinheiro.bolttech) on 2026-03-11, but iquirino.bolttech is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.0.48
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (iquirino.bolttech) than the most recent previously approved version (diogopinheiro.bolttech) on 2026-03-04, but iquirino.bolttech is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.43
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (iquirino.bolttech) than the most recent previously approved version (edirectamorim) on 2026-01-29, but iquirino.bolttech is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.0.42
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (edirectamorim) than the most recent previously approved version (iquirino.bolttech) on 2026-01-28, but edirectamorim is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.38
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (edirectamorim) than the most recent previously approved version (iquirino.bolttech) on 2026-01-07, but edirectamorim is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.35
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (iquirino.bolttech) than the most recent previously approved version (edirectamorim) on 2025-12-02, but iquirino.bolttech is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.