msluther / publish-cost Goto Github PK

• Dependency size

  • Is this easily done? Can we get this from various apis? various package managers might have something (e.g. npm)

• Does github have any apis for determining overall usage of CI/dependabot/snyk/various dependency bots/etc.

Readme needs to be updated with the motivation for this module. Basically there are real costs (planetary, monetary, mental) when packages are published.

Any defaults to various values need to be heavily cited from good sources.

APIs need to be documented.

Make a Changelog.

src directory
bin directory
test directory
eslint setup
test setup

What other inputs should there be to determine cost?

• Networking costs - electricity usage to upload the package, download on all the necessary machines, costs for internet nodes, etc.
• Package size
• Data center costs (physical space, AC costs)
• Personnel cost (employees that run the systems, there's a portion of their employment (albeit miniscule) that goes towards each of these)
• Anything else of interest?

Ironic yes, but this repo should have some sort of CI setup on it. Probably github actions. It should run eslint, tests. possibly automated npm publishes

cli library chosen and basic wireup

• Carbon footprint
• Electric usage (kwh)
• Monetary
• Human time cost

• How many packages depend on the current package (overall dependency)
• Rates of dependent packages with automated dependency updates
• Is this a publish for a security issue (drives whether automated dependency update)
• Average runtime of a CI build
• Average time to PR a dependency update
• Merge results in more CI
• Average electricity used for a CI build
• Average monetary cost per kwh
• Average carbon footprint per kwh