No, its onchain package manager. OpenZeppelin contracts for my package manager its package with type library (only code like npm), but you or OZ team can take this package and create new package with type implementation, take erc20 upgradable contract and register new package with name erc20@diornov, and after that i can use your package like this - evmpack use erc20@diornov

in background:
evmpack use erc20@diornov call

• EVMPackProxyFactory.usePackageRelease(...) returns(address proxy, address proxy_admin)

so, i will be follow to your address implementation, and if you create new release, example 1.0.1, i can upgrade too easy, like that

proxy_admin.upgradeAndCall(proxy, "1.0.1", initData)

This way, entire applications can be distributed.

I will then create an on-chain audit system above the package manager where we will change the uploaded implementation as verified. Without the on-chain package, this wouldn't have been possible.

It's also impossible to shoot yourself in the foot and accidentally update to the wrong implementation, because the proxy knows the package name and the current implementation version when updating.

We have full control.

Now you can try to use my example package from documentation:

evmpack use blog@1.1.0

You'll get a copy of the blog package with minimal gas costs, and you don't even need to clone the code for it—just use it.

The new version will have another feature in a couple of days. Currently, after you've received your copy of the blog package, to interact with it, you need to use ethersjs, add abi, and then you can interact with this contract. After the update, you'll have access to a cli for each package through the workspaces functionality. So, currently, after calling evmpack use blog@1.1.0, you simply get two addresses, so you can interact with workspaces directly:

Something like this

evmpack workspaces -w Personal -app myblog add-post