gocardless/angularjs-style-guide resource
AngularJS style guide used at GoCardless observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4370
- days_rel: n/a
- days_push: 2838
- n_releases_24m: 0
Adoption not part of the score
1433 stars · 55 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A style guide documenting GoCardless's conventions for writing AngularJS applications, covering directory structure, components, routes, testing, and ES6-oriented patterns. It is a documentation resource rather than runnable software.
Use cases
- structure an angularjs application codebase
- learn angularjs best practices and conventions
- set up an es6 angularjs project scaffold
- decide how to organize components and routes in angular
- adopt team coding standards for angularjs
When to choose
- you maintain or start a legacy AngularJS (1.x) codebase and want consistent conventions
- you want a reference for component-based folder structure and testing layout in AngularJS
When to avoid
- you are starting a new project with modern Angular (2+), React, or Vue
- you need actively maintained tooling - the guide and its ES6/SystemJS recommendations date from ~2018
Facets
learning-resource · maturity abandoned
documentation developer-tools web-development frontend tutorials browser angularjs style-guide coding-standards es6 best-practices javascript nodejs
1 source
- readme: https://github.com/gocardless/angularjs-style-guide · fetched 2026-08-28 · 66f8bf55fcfe
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| gocardless/angularjs-style-guide | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="gocardless/angularjs-style-guide")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem