“issues affecting subscribers” not clearing when a new stream replaces it

v0.11 of this package depends on npm v5, which has some CVEs. v0.12.0 no longer depends on npm, but:

  • the task for 0.11 having issues hasn’t cleared
  • the issues tab for 0.12 incorrectly claims it has npm and its transitive deps as vulnerable dependencies

@ljharb looks like this was a syncing issues and is now resolved, but please let me know if you continue to see any issues.

Thank you!

1 Like