Future of this library

Open
#797 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
angular, typescript

Research direction

Start by reviewing the README, EXAMPLES.md, API.md, and the issue history referenced in the report. The issue is complete only when the project's maintenance status, ownership plans, or official alternative are clearly communicated; it does not identify a code or documentation file to change.

Written by the indexing model from the issue text.

Description

Checklist
  • I have looked into the Readme and Examples, and have not found a suitable solution or answer.
  • I have looked into the API documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved

Hello,

First of all, thank you for your work on this library, which has been very useful to many developers, including myself.

I noticed that the repository has not been updated for some time. Could you please clarify if this library is no longer being actively maintained?

If that's the case, are there any plans to transfer ownership or provide an official alternative? Knowing the status of the project would help developers decide whether to continue using it or to migrate to another solution.

Thank you for your time and for all the effort you've put into this project.

Best regards,

Describe the ideal solution

info

Alternatives and current workarounds

No response

Additional context

No response

Dominant language
TypeScript
Stars
2.6k
Forks
472
PR merge metrics
No merged PRs in 30d

Getting set up

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.

More from auth0/angular2-jwt

All issues in auth0/angular2-jwt

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.