typisttech / typisttech/wp-org-closed-plugin

Potential issue with composer audit

Open
#71 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
6
Forks
1
Avg merge
2h 10m
Merged PRs (30d)
35

Description

Hello @tangrufus

Following the discussion regarding the package shutdown declaration by Roots for security reasons, I ran some tests on your extension and I believe there may be an issue related to Composer commands.

Current behavior:

  • composer install works correctly
  • composer require also works as expected
  • However, composer audit does not return any message or result
  • And composer update fails because Composer can no longer reach the wp-packages server

I have attached my composer.json and composer.lock files to help reproduce the issue.

Steps to reproduce:

  1. Install dependencies
  2. Run: composer audit

Then also test:
bash composer update

It seems there may either be an issue with the repository declaration or an unexpected behavior related to the shutdown / unavailability of wp-packages.

(I renamed the lock file .lock.json because I couldn't upload it.)

composer.json
composer.lock.json

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the attached composer.json and composer.lock.json files, then run composer install, composer audit, and composer update using the reported setup. Compare the empty audit result and update failure with the repository declaration and wp-packages availability; done means the behavior is reproducible and its cause or expected behavior is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
security, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.