corgibytes / freshli Goto Github PK

The Freshli-CLI project contains a lot of epics that would best live here. Good examples are the epics that track the creation of different language agents.

• corgibytes/freshli-cli#698
• corgibytes/freshli-cli#647
• corgibytes/freshli-cli#648
• corgibytes/freshli-cli#649

• Create the action
• Install the action in all of the repositories
  • freshli
  • freshli-web
  • freshli-ui
  • freshli-cli
  • freshli-agent-java
  • freshli-agent-dotnet
  • freshli-agent-python
  • freshli-agent-go
  • dependency-history-maven
  • versions-maven-plugin

Build out Python language support. Initially targeting the support for Ruby that existed in freshli-lib (analyzing requirements.txt files)

• Create GitHub repository for freshli-agent-python

(The following issues should be moved to the repository that's created above once it exists.)

• Add skeleton command line application
• Implement detect-manifest
• Implement process-manifest
• Implement validating-repositories
• Implement retrieve-release-history
• Implement validating-package-urls
• Validate against freshli agents verify command

(The following issue should belong to this project)

• Add freshli-agent-python to production docker container image

It can be difficult to determine if specific changes are included in the executable that someone has installed. To help with that difficulty, we need to add versions.

• corgibytes/freshli-cli#348
• corgibytes/freshli-agent-java#36
• corgibytes/freshli-agent-java#37
• corgibytes/freshli-cli#566

https://github.com/anchore/syft provides support for creating SBOM files for a wide variety of languages and frameworks, which might be worth exploring if and how it could help the https://github.com/corgibytes/freshli-cli process more repositories.

We have created a bunch of different terms and concepts in this project, but we're not always using them correctly. We also don't have a place for new folks to look to get up-to-speed with the project. Documenting these things in a .md file in the docs/ directory would help with that.

Once we have these terms defined, we can also open up separate issues wherever we see places in the code where the wrong names are being used.

There is currently no authoritative location for the gRPC service definition that is used by the CLI and the language agents. The file should be moved to this location, and each repository that needs a copy of the file should retrieve it as a build step.

• Remove the file from the Freshli CLI
• Remove the file from the Freshli Java Agent
• Remove the file from the Freshli Dotnet Agent
• Remove the file from the Freshli Python Agent

Use the latest version of the Contributor Covenenat.

• #21
• corgibytes/freshli-cli#619
• corgibytes/freshli-agent-dotnet#16
• corgibytes/freshli-agent-java#115
• corgibytes/freshli-agent-python#8
• corgibytes/freshli-agent-go#9
• corgibytes/dependency-history-maven#71
• corgibytes/freshli-commons#4

Since the CLI agents verify command is going to become the acceptance testing tool for language agents, this should just be a document that outlines the the details of what needs to be implemented in prose form. It should answer what needs to be implemented and why it needs to be implemented that way.

Many of the Freshli repositories are using Ruby as a command runner. There is some support code that has been copied from repository to repository, and that should be moved into a common place so that there is less chance of drift happening between the different versions.

The Freshli repositories that are for CLI programs are also using Cucumber and Aruba for testing. There are many Cucumber step implementations that have been copied from repository to repository as well. Those should be stored in a central location as well.

My first idea is to create a simple Ruby gem that is referenced via a github: parameter in the Gemfile for each Freshli project. That's probably the simplest way to go about doing this.

Build out Perl language support. Initially targeting the support for Perl that existed in freshli-lib (analyzing cpanfile)

• Create GitHub repository for freshli-agent-perl

(The following issues should be moved to the repository that's created above once it exists.)

• Add skeleton command line application
• Implement detect-manifest
• Implement process-manifest
• Implement validating-repositories
• Implement retrieve-release-history
• Implement validating-package-urls
• Validate against freshli agents verify command

(The following issue should belong to this project)

• Add freshli-agent-perl to production docker container image

• Maven support
• corgibytes/freshli-agent-java#116

Build out PHP language support. Initially targeting the support for PHP that existed in freshli-lib (analyzing composer.json and composer.lock).

• Create GitHub repository for freshli-agent-php

(The following issues should be moved to the repository that's created above once it exists.)

• Add skeleton command line application
• Implement detect-manifest
• Implement process-manifest
• Implement validating-repositories
• Implement retrieve-release-history
• Implement validating-package-urls
• Validate against freshli agents verify command

(The following issue should belong to this project)

• Add freshli-agent-php to production docker container image

Build out C# language support. Initially targeting the support for C# that existed in freshli-lib (analyzing *.csproj files).

• corgibytes/freshli-cli#557
• corgibytes/freshli-agent-dotnet#1
• corgibytes/freshli-agent-dotnet#7
• corgibytes/freshli-agent-dotnet#4
• corgibytes/freshli-cli#605
• corgibytes/freshli-agent-dotnet#9
• corgibytes/freshli-agent-dotnet#10
• corgibytes/freshli-cli#611
• corgibytes/freshli-cli#610
• corgibytes/freshli-agent-dotnet#13
• corgibytes/freshli-agent-dotnet#14

Build out Go language support.

• Create GitHub repository for freshli-agent-go

(The following issues should be moved to the repository that's created above once it exists.)

• Add skeleton command line application
• Implement detect-manifest
• Implement process-manifest
• Implement validating-repositories
• Implement retrieve-release-history
• Implement validating-package-urls
• Validate against freshli agents verify command

(The following issue should belong to this project)

• Add freshli-agent-go to production docker container image

Build out Rust language support.

• Create GitHub repository for freshli-agent-rust

(The following issues should be moved to the repository that's created above once it exists.)

• Add skeleton command line application
• Implement detect-manifest
• Implement process-manifest
• Implement validating-repositories
• Implement retrieve-release-history
• Implement validating-package-urls
• Validate against freshli agents verify command

(The following issue should belong to this project)

• Add freshli-agent-rust to production docker container image

Build out Ruby language support. Initially targeting the support for Ruby that existed in freshli-lib (analyzing Gemfile.lock)

• #30

(The following issues should be moved to the repository that's created above once it exists.)

• Add skeleton command line application
• Implement detect-manifest
• Implement process-manifest
• Implement validating-repositories
• Implement retrieve-release-history
• Implement validating-package-urls
• Validate against freshli agents verify command

(The following issue should belong to this project)

• Add freshli-agent-ruby to production docker container image

• corgibytes/freshli-cli#650
• #31
• corgibytes/freshli-cli#644
• corgibytes/freshli-cli#645
• corgibytes/freshli-cli#646

Build out JavaScript language support.

This should support both NPM and Yarn dependency manifest formats.

• Create GitHub repository for freshli-agent-javascript

(The following issues should be moved to the repository that's created above once it exists.)

• Add skeleton command line application
• Implement detect-manifest
• Implement process-manifest
• Implement validating-repositories
• Implement retrieve-release-history
• Implement validating-package-urls
• Validate against freshli agents verify command

(The following issue should belong to this project)

• Add freshli-agent-javascript to production docker container image