onedevatlasBeta
Browse the atlas
AllABAPCAPUI5BTP
PackagePackagetypeA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

abapPGP

An OpenPGP implementation in ABAP, scoped to signing and marked work in progress, whose own README warns that it will most certainly contain severe bugs and points to established PGP software.

abapPGP implements the OpenPGP standard in ABAP. Its stated scope is signing, under a heading that calls the project work in progress, with a link to an issue beside it. The Requirements section names one thing, the AES library by Sumu-Ning, and does not say what abapPGP uses it for. Nothing else on the page names an installation method, an ABAP release or a program to run.

GitHub10 ★
abaplint16,599 lines

Facts

Last pushLicenceMIT

Where it sits

Lives in
ABAP
Provides
Encryption and signingABAPEncryption and signingcapabilityEncrypting, decrypting and signing data from application code: a document wrapped for one recipient, a payload signed so its origin can be checked, a value enciphered with a key both sides hold. Encryption of a connection, TLS, is set up in the system and is outside this concern.
Requires
Sumu-Ning/AESSumu-Ning/AESartifactThe one entry under the README's Requirements heading, named by its repository address; the page does not say what abapPGP uses it for.

Who is behind it

Lars HvamLars HvamPersonMaintains this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpmaintainer

Before choosing this

Conditions

PracticalFunctional boundary

Not for anything important, which is the maintainer's own instruction: the README's Warning section calls it stupid to write your own encryption or PGP library, says abapPGP will most certainly contain severe bugs, and points instead at established PGP software such as OpenPGP. Signing is the only scope it states.

What it declares

Every artifact

Type
Package
Origin
Independently maintained

As a package

Where it runs
does not say
Distributed through
does not say

Connections2

README

quoted from larshp/abapPGP under MIT, read
larshp/abapPGP/README.mdOn GitHub

abapPGP

ABAP implementation of OpenPGP

Requirements

https://github.com/Sumu-Ning/AES

Work in progresss

Current scope is signing, see https://github.com/larshp/abapGit/issues/358

Warning

It is stupid to write your own encryption/PGP library, abapPGP will most certainly contain severe bugs.

Do not use this for anything important, instead use real PGP software like openPGP

MIT, read

Others providing3

Compare all 4 on the Encryption and signing page →
Encryption and signing
  1. SAP Keystore ServiceKey and certificate repository in SAP BTP's Neo data centresfrom BTP/BAIP
  2. hhelibeb/blowfish-abapBlowfish cipher in ABAP, ECB and CBC modesfrom ABAP
  3. Sumu-Ning/AESAES and Rijndael encryption utilities for ABAPfrom ABAP

Details

Sources3
Added by handdiscovered herechecked
github.com/larshp/abapPGPtree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, security-and-compliance
abaplint
issues under its own abaplint configuration0
lines16,599
statements8,870
objects91
files225
analysed, main
abaplint version2.120.84
read fromabaplint.app,
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:larshp-abappgp
JSON
/artifacts/larshp-abappgp.json
MCP
Connecting an agent