pyasn1 breaking changes
Every breaking API change we have recorded in pyasn1 on PyPI: 4 breaking changes in 4 versions. Below are its newest 4 versions, removals and renames first, each with its source.
Newest change October 27, 2026
On this page
0.6.5
- Behavior changed
Decoding nested constructed OCTET STRING fragments now includes their octets in the result, so code that relied on the earlier output may see different values. github.com
0.6.4
- Behavior changed
BER long-form tag IDs are limited to 20 octets (140 bits); substrate that previously decoded with longer tag IDs will now fail to decode. github.com
0.6.3
- Behavior changed
The ASN.1 decoder now rejects deeply nested structures beyond a new depth limit to prevent stack overflow. Code that decodes unusually deep structures may now get an error and may need to handle it. github.com
0.6.2
- Behavior changed
The decoder now rejects OID and RELATIVE-OID encodings with too many continuation octets, as a security fix for CVE-2026-23490. Code that decodes very long OIDs may now get an error where it previously succeeded. github.com
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp