name: Scorecards analysis
    runs-on: ubuntu-latest
    permissions:
      # Needed to upload the results to code-scanning dashboard.
      security-events: write
      # Needed to publish results and get a badge (see publish_results below).
      id-token: write

    steps:
      - name: "Checkout code"

Normalmente, o processo é que **você define** em seu código qual é a mensagem que você irá mandar, o **corpo da sua requisição**.

Você também define de alguma maneira em quais **momentos** a sua aplicação mandará essas requisições ou eventos.

E os **seus usuários** definem de alguma forma (em algum painel por exemplo) a **URL** que a sua aplicação deve enviar essas requisições.

	peerRESTReleaseInfo = "releaseinfo"
	peerRESTExecAt      = "exec-at"

	peerRESTListenBucket = "bucket"
	peerRESTListenPrefix = "prefix"
	peerRESTListenSuffix = "suffix"
	peerRESTListenEvents = "events"
	peerRESTLogMask      = "log-mask"
)

```
https://yourapi.com/invoices/?callback_url=https://www.external.org/events
```

JSON ボディは:

```JSON
{
    "id": "2expen51ve",
    "customer": "Mr. Richie Rich",
    "total": "9999"
}
```

その後 *あなたの API* は請求書を処理し、のちほど `callback_url`（*外部 API*）へコールバックのリクエストを送ります:

```
https://www.external.org/events/invoices/2expen51ve
```

JSON ボディは次のような内容です:

```JSON
{

    for (i in 0 until effects.callsToExecute.size) {
      val call = effects.callsToExecute[i]

      // If the newly-enqueued call is already out, skip its dispatcher queue events. We only
      // publish those events for calls that have to wait.
      if (call === enqueuedCall) {
        callDispatcherQueueStart = false
      } else {
        call.call.eventListener.dispatcherQueueEnd(call.call, this)
      }

		// Such events will not exist and wouldve been already been sent successfully.
		if os.IsNotExist(err) {
			return nil
		}
		return err
	}

	if err = target.send(eventData); err != nil {
		return err
	}

	// Delete the event from store.
	return target.store.Del(key)
}

// Save - saves the events to the store if queuestore is configured, which will

import org.apache.maven.execution.AbstractExecutionListener;
import org.apache.maven.execution.ExecutionEvent;
import org.apache.maven.execution.ExecutionListener;

/**
 * Forwards execution events to EventSpies.
 * @since 3.0.2
 */
class EventSpyExecutionListener extends AbstractExecutionListener {

    private final EventSpyDispatcher dispatcher;

    private final ExecutionListener delegate;

import org.apache.maven.artifact.resolver.ArtifactNotFoundException;
import org.apache.maven.artifact.resolver.ArtifactResolutionException;
import org.apache.maven.profiles.ProfileManager;
import org.apache.maven.wagon.events.TransferListener;

/**
 * @deprecated use {@link ProjectBuilder} instead
 */
@Deprecated
public interface MavenProjectBuilder {

/**
 * Hc5ConnectionMonitorTarget is responsible for monitoring and managing HTTP client connections
 * for Apache HttpComponents 5.x. It implements the TimeoutTarget interface to handle connection
 * expiration events.
 *
 * <p>This class uses an instance of HttpClientConnectionManager to manage the connections.
 * It closes expired connections and idle connections that have exceeded a specified timeout.
 * </p>
 *

import org.apache.maven.project.MavenProject;

/**
 * Holds data relevant for an execution event.
 *
 */
public interface ExecutionEvent {

    /**
     * The possible types of execution events.
     *
     * Note: do not modify this enum, or, make sure that this enum and
     * {@link org.apache.maven.api.EventType} have same elements in same order.
     */
    enum Type {
        ProjectDiscoveryStarted,