iamcal/oembed resource
The oEmbed Spec observed · 2026-08-28
Health v2 · maintenance only
77/100
- Activity 99
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 5813
- days_rel: n/a
- days_push: 8
- n_releases_24m: 0
Adoption not part of the score
1440 stars · 766 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
The canonical oEmbed specification website plus a machine-readable registry of oEmbed providers stored as YAML files. It is also published as the npm package 'oembed-providers' so consumers can ingest the provider list directly.
Use cases
- get a list of oEmbed providers for my app
- embed youtube and flickr links in my site
- look up the oembed endpoint for a url
- read the oembed spec
- convert a link into embeddable content data
When to choose
- you need the authoritative oEmbed spec or an up-to-date provider registry
- you're building an oEmbed consumer and want endpoint/scheme mappings without compiling them yourself
When to avoid
- you need a full oEmbed client library that performs requests and parses responses
- you need providers not listed in the official registry
Facets
dataset · maturity active
documentation yaml web-development apis documentation php oembed spec provider-registry npm-package embed-urls web-server nodejs
2 sources
- readme: https://github.com/iamcal/oembed · fetched 2026-08-28 · 11d5c4cb86b7
- homepage: http://oembed.com · fetched 2026-08-29 · 63b5840d3a0a
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| iamcal/oembed | main | 77 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem