Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Library/Project Seemingly Abandoned #14

Closed
ixis-doug opened this issue Feb 13, 2020 · 2 comments
Closed

Library/Project Seemingly Abandoned #14

ixis-doug opened this issue Feb 13, 2020 · 2 comments

Comments

@ixis-doug
Copy link

This library appears to have no maintainer; the last merge was in 2014. There is a PR (#8) open for nearly 3 years that fixes submodule paths. This library is still referenced in recent literature around the web wrt working with the (GTM) dataLayer, and its abandoned status should be clearly called out in the README or a new maintainer chosen.

@ixis-doug
Copy link
Author

Note there is also no bot keeping dependencies up-to-date

found 72 vulnerabilities (14 low, 21 moderate, 37 high)

@bnkuhn bnkuhn closed this as completed Feb 19, 2020
@ixis-doug
Copy link
Author

ixis-doug commented Feb 20, 2020

@bnkuhn merging #8 does not resolve this issue; that was just one example. If you try to pull down this repo and build it, you will run into a host issues...

  • various build scripts depend on python 2 (referenced as python -- this is an outdated assumption in most systems)
  • unclear what Java version is required for the closure compiler build process(es)
  • as mentioned in comment, 72 vulnerabilities in dependencies

Furthermore, the complicated build pipeline (which includes google-specific tooling such as the closure compiler) makes "fork and fix yourself" an impractical option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants