Executive summary
twilio/twilio-ruby is rated At risk because critical security findings are open. Its score is held back because we found no recorded design decisions and no architecture document or diagram, and 11 files are no longer known to anyone active in the project. It scores 62 out of 100, which the At risk rating leaves unchanged.
Maturity, at 56, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Having someone learn and document the 11 files no active contributor knows comes next, worth about 5 points. Raising Maturity to 70 would lift the score to about 66.
Three passwords or keys are open to anyone who can read the repository. Two secrets can leak from the build pipeline, and one known security hole in a package the code depends on can be used by attackers. Replacing each exposed password or key, limiting each secret to its own step and updating the vulnerable packages would close these risks. Pinning each tool to an exact version would fix the pipeline tool referenced by a changeable name, and giving the pull-request workflow read-only access would deal with the pipeline that outsiders can trigger with write access.
The product code is 5,662 lines, about €10,000 to rebuild.
If Maturity rose from 56 to 70, the lowest score rated Strong, the score would rise from 62 to about 66.
New since the last survey: 1 finding
- Cohesion (LCOM4) · Low cohesion: V1 (LCOM4 5) lib/twilio-ruby/rest/webhooks/v1.rb
Fixed since the last survey: 1 finding
- Web-Security Posture · Weak hash algorithm lib/twilio-ruby/security/request_validator.rb
Rebuild cost: about €10,000 · Estimate
| Cost to rebuild | €3,300 to €17,000, for 55 to 176 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,662 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 JWT | 2 REST | 3 REST.Api.V2010.AccountContext.AddressContext | 4 REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext | 5 REST.Api.V2010.AccountContext.CallContext | 6 REST.Api.V2010.AccountContext.ConferenceContext | 7 REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext | 8 REST.Api.V2010.AccountContext.MessageContext | 9 REST.Api.V2010.AccountContext.RecordingContext | 10 REST.Api.V2010.AccountContext.SipList | 11 REST.Chat.V1.ServiceContext | 12 REST.Chat.V2.ServiceContext | 13 REST.Conversations.V1.ConversationContext | 14 REST.Conversations.V1.ServiceContext.ConversationContext | 15 REST.Events.V1 | 16 REST.FlexApi.V1.InteractionContext | 17 REST.Insights.V1 | 18 REST.IpMessaging.V1.ServiceContext | 19 REST.IpMessaging.V2.ServiceContext | 20 REST.Marketplace.V1 | 21 REST.Messaging.V1 | 22 REST.Preview.Marketplace | 23 REST.Proxy.V1.ServiceContext.SessionContext | 24 REST.Serverless.V1.ServiceContext | 25 REST.Studio.V1.FlowContext | 26 REST.Studio.V2.FlowContext | 27 REST.Supersim.V1 | 28 REST.Sync.V1.ServiceContext | 29 REST.Taskrouter.V1.WorkspaceContext | 30 REST.Trusthub.V1 | 31 REST.Verify.V2.ServiceContext.EntityContext | 32 REST.Video.V1.RoomContext | 33 REST.Api.V2010.AccountContext.IncomingPhoneNumberContext | 34 REST.Conversations.V1.ServiceContext | 35 REST.FlexApi.V1 | 36 REST.Proxy.V1.ServiceContext | 37 REST.Verify.V2.ServiceContext | 38 REST.Api.V2010.AccountContext | 39 REST.Conversations.V1 | 40 REST.Api.V2010 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 JWT | ||||||||||||||||||||||||||||||||||||||||
| 2 REST | ||||||||||||||||||||||||||||||||||||||||
| 3 REST.Api.V2010.AccountContext.AddressContext | 5 | |||||||||||||||||||||||||||||||||||||||
| 4 REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext | 35 | |||||||||||||||||||||||||||||||||||||||
| 5 REST.Api.V2010.AccountContext.CallContext | 52 | |||||||||||||||||||||||||||||||||||||||
| 6 REST.Api.V2010.AccountContext.ConferenceContext | 14 | |||||||||||||||||||||||||||||||||||||||
| 7 REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext | 7 | |||||||||||||||||||||||||||||||||||||||
| 8 REST.Api.V2010.AccountContext.MessageContext | 10 | |||||||||||||||||||||||||||||||||||||||
| 9 REST.Api.V2010.AccountContext.RecordingContext | 14 | |||||||||||||||||||||||||||||||||||||||
| 10 REST.Api.V2010.AccountContext.SipList | 21 | |||||||||||||||||||||||||||||||||||||||
| 11 REST.Chat.V1.ServiceContext | 21 | |||||||||||||||||||||||||||||||||||||||
| 12 REST.Chat.V2.ServiceContext | 28 | |||||||||||||||||||||||||||||||||||||||
| 13 REST.Conversations.V1.ConversationContext | 21 | |||||||||||||||||||||||||||||||||||||||
| 14 REST.Conversations.V1.ServiceContext.ConversationContext | 21 | |||||||||||||||||||||||||||||||||||||||
| 15 REST.Events.V1 | 27 | |||||||||||||||||||||||||||||||||||||||
| 16 REST.FlexApi.V1.InteractionContext | 7 | |||||||||||||||||||||||||||||||||||||||
| 17 REST.Insights.V1 | 31 | |||||||||||||||||||||||||||||||||||||||
| 18 REST.IpMessaging.V1.ServiceContext | 21 | |||||||||||||||||||||||||||||||||||||||
| 19 REST.IpMessaging.V2.ServiceContext | 28 | |||||||||||||||||||||||||||||||||||||||
| 20 REST.Marketplace.V1 | 26 | |||||||||||||||||||||||||||||||||||||||
| 21 REST.Messaging.V1 | 75 | |||||||||||||||||||||||||||||||||||||||
| 22 REST.Preview.Marketplace | 14 | |||||||||||||||||||||||||||||||||||||||
| 23 REST.Proxy.V1.ServiceContext.SessionContext | 14 | |||||||||||||||||||||||||||||||||||||||
| 24 REST.Serverless.V1.ServiceContext | 28 | |||||||||||||||||||||||||||||||||||||||
| 25 REST.Studio.V1.FlowContext | 14 | |||||||||||||||||||||||||||||||||||||||
| 26 REST.Studio.V2.FlowContext | 20 | |||||||||||||||||||||||||||||||||||||||
| 27 REST.Supersim.V1 | 59 | |||||||||||||||||||||||||||||||||||||||
| 28 REST.Sync.V1.ServiceContext | 28 | |||||||||||||||||||||||||||||||||||||||
| 29 REST.Taskrouter.V1.WorkspaceContext | 67 | |||||||||||||||||||||||||||||||||||||||
| 30 REST.Trusthub.V1 | 88 | |||||||||||||||||||||||||||||||||||||||
| 31 REST.Verify.V2.ServiceContext.EntityContext | 17 | |||||||||||||||||||||||||||||||||||||||
| 32 REST.Video.V1.RoomContext | 24 | |||||||||||||||||||||||||||||||||||||||
| 33 REST.Api.V2010.AccountContext.IncomingPhoneNumberContext | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 REST.Conversations.V1.ServiceContext | 42 | 3 | ||||||||||||||||||||||||||||||||||||||
| 35 REST.FlexApi.V1 | 139 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 REST.Proxy.V1.ServiceContext | 14 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 REST.Verify.V2.ServiceContext | 58 | 3 | ||||||||||||||||||||||||||||||||||||||
| 38 REST.Api.V2010.AccountContext | 140 | 1 | 7 | 9 | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 39 REST.Conversations.V1 | 56 | 3 | 6 | |||||||||||||||||||||||||||||||||||||
| 40 REST.Api.V2010 | 7 | 24 |
3→2 REST.Api.V2010.AccountContext.AddressContext uses REST✕
- Connections
- 5 pairs of types, where a type in REST.Api.V2010.AccountContext.AddressContext uses a type in REST.
- The types involved
Twilio.REST.Api.V2010.AccountContext.AddressContext.DependentPhoneNumberInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AddressContext.DependentPhoneNumberList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.AddressContext.DependentPhoneNumberListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.AddressContext.DependentPhoneNumberPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.AddressContext.DependentPhoneNumberPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.AddressContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext.AddressContext, while a change to REST.Api.V2010.AccountContext.AddressContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.AddressContext uses a module listed above it, which is the healthy direction.
4→2 REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext uses REST✕
- Connections
- 35 pairs of types, where a type in REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.LocalInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.LocalList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.LocalListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.LocalPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.LocalPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MachineToMachineInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MachineToMachineList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MachineToMachineListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MachineToMachinePage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MachineToMachinePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MobileInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MobileList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MobileListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MobilePage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MobilePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.NationalInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.NationalList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.NationalListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.NationalPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.NationalPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.SharedCostInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.SharedCostList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.SharedCostListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.SharedCostPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.SharedCostPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext, while a change to REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext uses a module listed above it, which is the healthy direction.
5→2 REST.Api.V2010.AccountContext.CallContext uses REST✕
- Connections
- 52 pairs of types, where a type in REST.Api.V2010.AccountContext.CallContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Api.V2010.AccountContext.CallContext.EventInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.CallContext.EventList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.CallContext.EventListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.CallContext.EventPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.CallContext.EventPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.CallContext.NotificationContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.CallContext.NotificationInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.CallContext.NotificationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.CallContext.NotificationList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.CallContext.NotificationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.CallContext.NotificationPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.CallContext.NotificationPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.CallContext.PaymentContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.CallContext.PaymentInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.CallContext.PaymentInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.CallContext.PaymentList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.CallContext.PaymentListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.CallContext.PaymentPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.CallContext.RecordingContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.CallContext.RecordingInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.CallContext.RecordingInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.CallContext.RecordingList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.CallContext.RecordingListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.CallContext.RecordingPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.CallContext.RecordingPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.CallContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext.CallContext, while a change to REST.Api.V2010.AccountContext.CallContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.CallContext uses a module listed above it, which is the healthy direction.
6→2 REST.Api.V2010.AccountContext.ConferenceContext uses REST✕
- Connections
- 14 pairs of types, where a type in REST.Api.V2010.AccountContext.ConferenceContext uses a type in REST.
- The types involved
Twilio.REST.Api.V2010.AccountContext.ConferenceContext.ParticipantContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.ConferenceContext.ParticipantInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.ConferenceContext.ParticipantInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.ConferenceContext.ParticipantList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.ConferenceContext.ParticipantListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.ConferenceContext.ParticipantPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.ConferenceContext.ParticipantPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.ConferenceContext.RecordingContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.ConferenceContext.RecordingInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.ConferenceContext.RecordingInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.ConferenceContext.RecordingList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.ConferenceContext.RecordingListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.ConferenceContext.RecordingPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.ConferenceContext.RecordingPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.ConferenceContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext.ConferenceContext, while a change to REST.Api.V2010.AccountContext.ConferenceContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.ConferenceContext uses a module listed above it, which is the healthy direction.
7→2 REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext uses REST✕
- Connections
- 7 pairs of types, where a type in REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext uses a type in REST.
- The types involved
Twilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.AssignedAddOnExtensionContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.AssignedAddOnExtensionInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.AssignedAddOnExtensionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.AssignedAddOnExtensionList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.AssignedAddOnExtensionListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.AssignedAddOnExtensionPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.AssignedAddOnExtensionPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext, while a change to REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext uses a module listed above it, which is the healthy direction.
8→2 REST.Api.V2010.AccountContext.MessageContext uses REST✕
- Connections
- 10 pairs of types, where a type in REST.Api.V2010.AccountContext.MessageContext uses a type in REST.
- The types involved
Twilio.REST.Api.V2010.AccountContext.MessageContext.FeedbackInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.MessageContext.FeedbackList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.MessageContext.FeedbackPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.MessageContext.MediaContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.MessageContext.MediaInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.MessageContext.MediaInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.MessageContext.MediaList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.MessageContext.MediaListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.MessageContext.MediaPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.MessageContext.MediaPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.MessageContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext.MessageContext, while a change to REST.Api.V2010.AccountContext.MessageContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.MessageContext uses a module listed above it, which is the healthy direction.
9→2 REST.Api.V2010.AccountContext.RecordingContext uses REST✕
- Connections
- 14 pairs of types, where a type in REST.Api.V2010.AccountContext.RecordingContext uses a type in REST.
- The types involved
Twilio.REST.Api.V2010.AccountContext.RecordingContext.AddOnResultContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.RecordingContext.AddOnResultInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.RecordingContext.AddOnResultInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.RecordingContext.AddOnResultList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.RecordingContext.AddOnResultListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.RecordingContext.AddOnResultPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.RecordingContext.AddOnResultPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.RecordingContext.TranscriptionContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.RecordingContext.TranscriptionInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.RecordingContext.TranscriptionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.RecordingContext.TranscriptionList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.RecordingContext.TranscriptionListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.RecordingContext.TranscriptionPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.RecordingContext.TranscriptionPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.RecordingContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext.RecordingContext, while a change to REST.Api.V2010.AccountContext.RecordingContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.RecordingContext uses a module listed above it, which is the healthy direction.
10→2 REST.Api.V2010.AccountContext.SipList uses REST✕
- Connections
- 21 pairs of types, where a type in REST.Api.V2010.AccountContext.SipList uses a type in REST.
- The types involved
Twilio.REST.Api.V2010.AccountContext.SipList.CredentialListContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.SipList.CredentialListInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.SipList.CredentialListInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.SipList.CredentialListList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.SipList.CredentialListListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.SipList.CredentialListPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.SipList.CredentialListPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.SipList.DomainContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.SipList.DomainInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.SipList.DomainInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.SipList.DomainList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.SipList.DomainListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.SipList.DomainPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.SipList.DomainPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.SipList.IpAccessControlListContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.SipList.IpAccessControlListInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.SipList.IpAccessControlListInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.SipList.IpAccessControlListList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.SipList.IpAccessControlListListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.SipList.IpAccessControlListPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.SipList.IpAccessControlListPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.SipList uses REST, so a change to REST can break REST.Api.V2010.AccountContext.SipList, while a change to REST.Api.V2010.AccountContext.SipList can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.SipList uses a module listed above it, which is the healthy direction.
11→2 REST.Chat.V1.ServiceContext uses REST✕
- Connections
- 21 pairs of types, where a type in REST.Chat.V1.ServiceContext uses a type in REST.
- The types involved
Twilio.REST.Chat.V1.ServiceContext.ChannelContext→Twilio.REST.InstanceContextTwilio.REST.Chat.V1.ServiceContext.ChannelInstance→Twilio.REST.InstanceResourceTwilio.REST.Chat.V1.ServiceContext.ChannelInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Chat.V1.ServiceContext.ChannelList→Twilio.REST.ListResourceTwilio.REST.Chat.V1.ServiceContext.ChannelListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Chat.V1.ServiceContext.ChannelPage→Twilio.REST.PageTwilio.REST.Chat.V1.ServiceContext.ChannelPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Chat.V1.ServiceContext.RoleContext→Twilio.REST.InstanceContextTwilio.REST.Chat.V1.ServiceContext.RoleInstance→Twilio.REST.InstanceResourceTwilio.REST.Chat.V1.ServiceContext.RoleInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Chat.V1.ServiceContext.RoleList→Twilio.REST.ListResourceTwilio.REST.Chat.V1.ServiceContext.RoleListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Chat.V1.ServiceContext.RolePage→Twilio.REST.PageTwilio.REST.Chat.V1.ServiceContext.RolePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Chat.V1.ServiceContext.UserContext→Twilio.REST.InstanceContextTwilio.REST.Chat.V1.ServiceContext.UserInstance→Twilio.REST.InstanceResourceTwilio.REST.Chat.V1.ServiceContext.UserInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Chat.V1.ServiceContext.UserList→Twilio.REST.ListResourceTwilio.REST.Chat.V1.ServiceContext.UserListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Chat.V1.ServiceContext.UserPage→Twilio.REST.PageTwilio.REST.Chat.V1.ServiceContext.UserPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Chat.V1.ServiceContext uses REST, so a change to REST can break REST.Chat.V1.ServiceContext, while a change to REST.Chat.V1.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.Chat.V1.ServiceContext uses a module listed above it, which is the healthy direction.
12→2 REST.Chat.V2.ServiceContext uses REST✕
- Connections
- 28 pairs of types, where a type in REST.Chat.V2.ServiceContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Chat.V2.ServiceContext.BindingContext→Twilio.REST.InstanceContextTwilio.REST.Chat.V2.ServiceContext.BindingInstance→Twilio.REST.InstanceResourceTwilio.REST.Chat.V2.ServiceContext.BindingInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Chat.V2.ServiceContext.BindingList→Twilio.REST.ListResourceTwilio.REST.Chat.V2.ServiceContext.BindingListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Chat.V2.ServiceContext.BindingPage→Twilio.REST.PageTwilio.REST.Chat.V2.ServiceContext.BindingPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Chat.V2.ServiceContext.ChannelContext→Twilio.REST.InstanceContextTwilio.REST.Chat.V2.ServiceContext.ChannelInstance→Twilio.REST.InstanceResourceTwilio.REST.Chat.V2.ServiceContext.ChannelInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Chat.V2.ServiceContext.ChannelList→Twilio.REST.ListResourceTwilio.REST.Chat.V2.ServiceContext.ChannelListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Chat.V2.ServiceContext.ChannelPage→Twilio.REST.PageTwilio.REST.Chat.V2.ServiceContext.ChannelPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Chat.V2.ServiceContext.RoleContext→Twilio.REST.InstanceContextTwilio.REST.Chat.V2.ServiceContext.RoleInstance→Twilio.REST.InstanceResourceTwilio.REST.Chat.V2.ServiceContext.RoleInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Chat.V2.ServiceContext.RoleList→Twilio.REST.ListResourceTwilio.REST.Chat.V2.ServiceContext.RoleListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Chat.V2.ServiceContext.RolePage→Twilio.REST.PageTwilio.REST.Chat.V2.ServiceContext.RolePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Chat.V2.ServiceContext.UserContext→Twilio.REST.InstanceContextTwilio.REST.Chat.V2.ServiceContext.UserInstance→Twilio.REST.InstanceResourceTwilio.REST.Chat.V2.ServiceContext.UserInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Chat.V2.ServiceContext.UserList→Twilio.REST.ListResource
- Direction
- REST.Chat.V2.ServiceContext uses REST, so a change to REST can break REST.Chat.V2.ServiceContext, while a change to REST.Chat.V2.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.Chat.V2.ServiceContext uses a module listed above it, which is the healthy direction.
13→2 REST.Conversations.V1.ConversationContext uses REST✕
- Connections
- 21 pairs of types, where a type in REST.Conversations.V1.ConversationContext uses a type in REST.
- The types involved
Twilio.REST.Conversations.V1.ConversationContext.MessageContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ConversationContext.MessageInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ConversationContext.MessageInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ConversationContext.MessageList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ConversationContext.MessageListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ConversationContext.MessagePage→Twilio.REST.PageTwilio.REST.Conversations.V1.ConversationContext.MessagePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Conversations.V1.ConversationContext.ParticipantContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ConversationContext.ParticipantInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ConversationContext.ParticipantInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ConversationContext.ParticipantList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ConversationContext.ParticipantListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ConversationContext.ParticipantPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ConversationContext.ParticipantPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Conversations.V1.ConversationContext.WebhookContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ConversationContext.WebhookInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ConversationContext.WebhookInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ConversationContext.WebhookList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ConversationContext.WebhookListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ConversationContext.WebhookPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ConversationContext.WebhookPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Conversations.V1.ConversationContext uses REST, so a change to REST can break REST.Conversations.V1.ConversationContext, while a change to REST.Conversations.V1.ConversationContext can't break REST.
- Position
- Below the diagonal: REST.Conversations.V1.ConversationContext uses a module listed above it, which is the healthy direction.
14→2 REST.Conversations.V1.ServiceContext.ConversationContext uses REST✕
- Connections
- 21 pairs of types, where a type in REST.Conversations.V1.ServiceContext.ConversationContext uses a type in REST.
- The types involved
Twilio.REST.Conversations.V1.ServiceContext.ConversationContext.MessageContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.MessageInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.MessageInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.MessageList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.MessageListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.MessagePage→Twilio.REST.PageTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.MessagePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.ParticipantContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.ParticipantInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.ParticipantInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.ParticipantList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.ParticipantListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.ParticipantPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.ParticipantPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.WebhookContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.WebhookInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.WebhookInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.WebhookList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.WebhookListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.WebhookPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ServiceContext.ConversationContext.WebhookPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Conversations.V1.ServiceContext.ConversationContext uses REST, so a change to REST can break REST.Conversations.V1.ServiceContext.ConversationContext, while a change to REST.Conversations.V1.ServiceContext.ConversationContext can't break REST.
- Position
- Below the diagonal: REST.Conversations.V1.ServiceContext.ConversationContext uses a module listed above it, which is the healthy direction.
15→2 REST.Events.V1 uses REST✕
- Connections
- 27 pairs of types, where a type in REST.Events.V1 uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Events.V1.EventTypeContext→Twilio.REST.InstanceContextTwilio.REST.Events.V1.EventTypeInstance→Twilio.REST.InstanceResourceTwilio.REST.Events.V1.EventTypeInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Events.V1.EventTypeList→Twilio.REST.ListResourceTwilio.REST.Events.V1.EventTypeListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Events.V1.EventTypePage→Twilio.REST.PageTwilio.REST.Events.V1.EventTypePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Events.V1.SchemaContext→Twilio.REST.InstanceContextTwilio.REST.Events.V1.SchemaInstance→Twilio.REST.InstanceResourceTwilio.REST.Events.V1.SchemaInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Events.V1.SchemaList→Twilio.REST.ListResourceTwilio.REST.Events.V1.SchemaListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Events.V1.SchemaPage→Twilio.REST.PageTwilio.REST.Events.V1.SinkContext→Twilio.REST.InstanceContextTwilio.REST.Events.V1.SinkInstance→Twilio.REST.InstanceResourceTwilio.REST.Events.V1.SinkInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Events.V1.SinkList→Twilio.REST.ListResourceTwilio.REST.Events.V1.SinkListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Events.V1.SinkPage→Twilio.REST.PageTwilio.REST.Events.V1.SinkPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Events.V1.SubscriptionContext→Twilio.REST.InstanceContextTwilio.REST.Events.V1.SubscriptionInstance→Twilio.REST.InstanceResourceTwilio.REST.Events.V1.SubscriptionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Events.V1.SubscriptionList→Twilio.REST.ListResourceTwilio.REST.Events.V1.SubscriptionListResponse→Twilio.REST.InstanceListResource
- Direction
- REST.Events.V1 uses REST, so a change to REST can break REST.Events.V1, while a change to REST.Events.V1 can't break REST.
- Position
- Below the diagonal: REST.Events.V1 uses a module listed above it, which is the healthy direction.
16→2 REST.FlexApi.V1.InteractionContext uses REST✕
- Connections
- 7 pairs of types, where a type in REST.FlexApi.V1.InteractionContext uses a type in REST.
- The types involved
Twilio.REST.FlexApi.V1.InteractionContext.InteractionChannelContext→Twilio.REST.InstanceContextTwilio.REST.FlexApi.V1.InteractionContext.InteractionChannelInstance→Twilio.REST.InstanceResourceTwilio.REST.FlexApi.V1.InteractionContext.InteractionChannelInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.FlexApi.V1.InteractionContext.InteractionChannelList→Twilio.REST.ListResourceTwilio.REST.FlexApi.V1.InteractionContext.InteractionChannelListResponse→Twilio.REST.InstanceListResourceTwilio.REST.FlexApi.V1.InteractionContext.InteractionChannelPage→Twilio.REST.PageTwilio.REST.FlexApi.V1.InteractionContext.InteractionChannelPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.FlexApi.V1.InteractionContext uses REST, so a change to REST can break REST.FlexApi.V1.InteractionContext, while a change to REST.FlexApi.V1.InteractionContext can't break REST.
- Position
- Below the diagonal: REST.FlexApi.V1.InteractionContext uses a module listed above it, which is the healthy direction.
17→2 REST.Insights.V1 uses REST✕
- Connections
- 31 pairs of types, where a type in REST.Insights.V1 uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Insights.V1.CallContext→Twilio.REST.InstanceContextTwilio.REST.Insights.V1.CallInstance→Twilio.REST.InstanceResourceTwilio.REST.Insights.V1.CallInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Insights.V1.CallList→Twilio.REST.ListResourceTwilio.REST.Insights.V1.CallListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Insights.V1.CallPage→Twilio.REST.PageTwilio.REST.Insights.V1.CallSummariesInstance→Twilio.REST.InstanceResourceTwilio.REST.Insights.V1.CallSummariesList→Twilio.REST.ListResourceTwilio.REST.Insights.V1.CallSummariesListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Insights.V1.CallSummariesPage→Twilio.REST.PageTwilio.REST.Insights.V1.CallSummariesPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Insights.V1.ConferenceContext→Twilio.REST.InstanceContextTwilio.REST.Insights.V1.ConferenceInstance→Twilio.REST.InstanceResourceTwilio.REST.Insights.V1.ConferenceInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Insights.V1.ConferenceList→Twilio.REST.ListResourceTwilio.REST.Insights.V1.ConferenceListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Insights.V1.ConferencePage→Twilio.REST.PageTwilio.REST.Insights.V1.ConferencePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Insights.V1.RoomContext→Twilio.REST.InstanceContextTwilio.REST.Insights.V1.RoomInstance→Twilio.REST.InstanceResourceTwilio.REST.Insights.V1.RoomInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Insights.V1.RoomList→Twilio.REST.ListResourceTwilio.REST.Insights.V1.RoomListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Insights.V1.RoomPage→Twilio.REST.PageTwilio.REST.Insights.V1.RoomPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Insights.V1 uses REST, so a change to REST can break REST.Insights.V1, while a change to REST.Insights.V1 can't break REST.
- Position
- Below the diagonal: REST.Insights.V1 uses a module listed above it, which is the healthy direction.
18→2 REST.IpMessaging.V1.ServiceContext uses REST✕
- Connections
- 21 pairs of types, where a type in REST.IpMessaging.V1.ServiceContext uses a type in REST.
- The types involved
Twilio.REST.IpMessaging.V1.ServiceContext.ChannelContext→Twilio.REST.InstanceContextTwilio.REST.IpMessaging.V1.ServiceContext.ChannelInstance→Twilio.REST.InstanceResourceTwilio.REST.IpMessaging.V1.ServiceContext.ChannelInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.IpMessaging.V1.ServiceContext.ChannelList→Twilio.REST.ListResourceTwilio.REST.IpMessaging.V1.ServiceContext.ChannelListResponse→Twilio.REST.InstanceListResourceTwilio.REST.IpMessaging.V1.ServiceContext.ChannelPage→Twilio.REST.PageTwilio.REST.IpMessaging.V1.ServiceContext.ChannelPageMetadata→Twilio.REST.PageMetadataTwilio.REST.IpMessaging.V1.ServiceContext.RoleContext→Twilio.REST.InstanceContextTwilio.REST.IpMessaging.V1.ServiceContext.RoleInstance→Twilio.REST.InstanceResourceTwilio.REST.IpMessaging.V1.ServiceContext.RoleInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.IpMessaging.V1.ServiceContext.RoleList→Twilio.REST.ListResourceTwilio.REST.IpMessaging.V1.ServiceContext.RoleListResponse→Twilio.REST.InstanceListResourceTwilio.REST.IpMessaging.V1.ServiceContext.RolePage→Twilio.REST.PageTwilio.REST.IpMessaging.V1.ServiceContext.RolePageMetadata→Twilio.REST.PageMetadataTwilio.REST.IpMessaging.V1.ServiceContext.UserContext→Twilio.REST.InstanceContextTwilio.REST.IpMessaging.V1.ServiceContext.UserInstance→Twilio.REST.InstanceResourceTwilio.REST.IpMessaging.V1.ServiceContext.UserInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.IpMessaging.V1.ServiceContext.UserList→Twilio.REST.ListResourceTwilio.REST.IpMessaging.V1.ServiceContext.UserListResponse→Twilio.REST.InstanceListResourceTwilio.REST.IpMessaging.V1.ServiceContext.UserPage→Twilio.REST.PageTwilio.REST.IpMessaging.V1.ServiceContext.UserPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.IpMessaging.V1.ServiceContext uses REST, so a change to REST can break REST.IpMessaging.V1.ServiceContext, while a change to REST.IpMessaging.V1.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.IpMessaging.V1.ServiceContext uses a module listed above it, which is the healthy direction.
19→2 REST.IpMessaging.V2.ServiceContext uses REST✕
- Connections
- 28 pairs of types, where a type in REST.IpMessaging.V2.ServiceContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.IpMessaging.V2.ServiceContext.BindingContext→Twilio.REST.InstanceContextTwilio.REST.IpMessaging.V2.ServiceContext.BindingInstance→Twilio.REST.InstanceResourceTwilio.REST.IpMessaging.V2.ServiceContext.BindingInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.IpMessaging.V2.ServiceContext.BindingList→Twilio.REST.ListResourceTwilio.REST.IpMessaging.V2.ServiceContext.BindingListResponse→Twilio.REST.InstanceListResourceTwilio.REST.IpMessaging.V2.ServiceContext.BindingPage→Twilio.REST.PageTwilio.REST.IpMessaging.V2.ServiceContext.BindingPageMetadata→Twilio.REST.PageMetadataTwilio.REST.IpMessaging.V2.ServiceContext.ChannelContext→Twilio.REST.InstanceContextTwilio.REST.IpMessaging.V2.ServiceContext.ChannelInstance→Twilio.REST.InstanceResourceTwilio.REST.IpMessaging.V2.ServiceContext.ChannelInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.IpMessaging.V2.ServiceContext.ChannelList→Twilio.REST.ListResourceTwilio.REST.IpMessaging.V2.ServiceContext.ChannelListResponse→Twilio.REST.InstanceListResourceTwilio.REST.IpMessaging.V2.ServiceContext.ChannelPage→Twilio.REST.PageTwilio.REST.IpMessaging.V2.ServiceContext.ChannelPageMetadata→Twilio.REST.PageMetadataTwilio.REST.IpMessaging.V2.ServiceContext.RoleContext→Twilio.REST.InstanceContextTwilio.REST.IpMessaging.V2.ServiceContext.RoleInstance→Twilio.REST.InstanceResourceTwilio.REST.IpMessaging.V2.ServiceContext.RoleInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.IpMessaging.V2.ServiceContext.RoleList→Twilio.REST.ListResourceTwilio.REST.IpMessaging.V2.ServiceContext.RoleListResponse→Twilio.REST.InstanceListResourceTwilio.REST.IpMessaging.V2.ServiceContext.RolePage→Twilio.REST.PageTwilio.REST.IpMessaging.V2.ServiceContext.RolePageMetadata→Twilio.REST.PageMetadataTwilio.REST.IpMessaging.V2.ServiceContext.UserContext→Twilio.REST.InstanceContextTwilio.REST.IpMessaging.V2.ServiceContext.UserInstance→Twilio.REST.InstanceResourceTwilio.REST.IpMessaging.V2.ServiceContext.UserInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.IpMessaging.V2.ServiceContext.UserList→Twilio.REST.ListResource
- Direction
- REST.IpMessaging.V2.ServiceContext uses REST, so a change to REST can break REST.IpMessaging.V2.ServiceContext, while a change to REST.IpMessaging.V2.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.IpMessaging.V2.ServiceContext uses a module listed above it, which is the healthy direction.
20→2 REST.Marketplace.V1 uses REST✕
- Connections
- 26 pairs of types, where a type in REST.Marketplace.V1 uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Marketplace.V1.AvailableAddOnContext→Twilio.REST.InstanceContextTwilio.REST.Marketplace.V1.AvailableAddOnInstance→Twilio.REST.InstanceResourceTwilio.REST.Marketplace.V1.AvailableAddOnInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Marketplace.V1.AvailableAddOnList→Twilio.REST.ListResourceTwilio.REST.Marketplace.V1.AvailableAddOnListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Marketplace.V1.AvailableAddOnPage→Twilio.REST.PageTwilio.REST.Marketplace.V1.AvailableAddOnPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Marketplace.V1.InstalledAddOnContext→Twilio.REST.InstanceContextTwilio.REST.Marketplace.V1.InstalledAddOnInstance→Twilio.REST.InstanceResourceTwilio.REST.Marketplace.V1.InstalledAddOnInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Marketplace.V1.InstalledAddOnList→Twilio.REST.ListResourceTwilio.REST.Marketplace.V1.InstalledAddOnListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Marketplace.V1.InstalledAddOnPage→Twilio.REST.PageTwilio.REST.Marketplace.V1.InstalledAddOnPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Marketplace.V1.ModuleDataInstance→Twilio.REST.InstanceResourceTwilio.REST.Marketplace.V1.ModuleDataList→Twilio.REST.ListResourceTwilio.REST.Marketplace.V1.ModuleDataManagementContext→Twilio.REST.InstanceContextTwilio.REST.Marketplace.V1.ModuleDataManagementInstance→Twilio.REST.InstanceResourceTwilio.REST.Marketplace.V1.ModuleDataManagementInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Marketplace.V1.ModuleDataManagementList→Twilio.REST.ListResourceTwilio.REST.Marketplace.V1.ModuleDataManagementListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Marketplace.V1.ModuleDataManagementPage→Twilio.REST.PageTwilio.REST.Marketplace.V1.ModuleDataPage→Twilio.REST.PageTwilio.REST.Marketplace.V1.ReferralConversionInstance→Twilio.REST.InstanceResourceTwilio.REST.Marketplace.V1.ReferralConversionList→Twilio.REST.ListResource
- Direction
- REST.Marketplace.V1 uses REST, so a change to REST can break REST.Marketplace.V1, while a change to REST.Marketplace.V1 can't break REST.
- Position
- Below the diagonal: REST.Marketplace.V1 uses a module listed above it, which is the healthy direction.
21→2 REST.Messaging.V1 uses REST✕
- Connections
- 75 pairs of types, where a type in REST.Messaging.V1 uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Messaging.V1.BrandRegistrationContext→Twilio.REST.InstanceContextTwilio.REST.Messaging.V1.BrandRegistrationInstance→Twilio.REST.InstanceResourceTwilio.REST.Messaging.V1.BrandRegistrationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Messaging.V1.BrandRegistrationList→Twilio.REST.ListResourceTwilio.REST.Messaging.V1.BrandRegistrationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Messaging.V1.BrandRegistrationPage→Twilio.REST.PageTwilio.REST.Messaging.V1.BrandRegistrationPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Messaging.V1.DeactivationsContext→Twilio.REST.InstanceContextTwilio.REST.Messaging.V1.DeactivationsInstance→Twilio.REST.InstanceResourceTwilio.REST.Messaging.V1.DeactivationsInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Messaging.V1.DeactivationsList→Twilio.REST.ListResourceTwilio.REST.Messaging.V1.DeactivationsListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Messaging.V1.DeactivationsPage→Twilio.REST.PageTwilio.REST.Messaging.V1.DomainCertsContext→Twilio.REST.InstanceContextTwilio.REST.Messaging.V1.DomainCertsInstance→Twilio.REST.InstanceResourceTwilio.REST.Messaging.V1.DomainCertsInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Messaging.V1.DomainCertsList→Twilio.REST.ListResourceTwilio.REST.Messaging.V1.DomainCertsListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Messaging.V1.DomainCertsPage→Twilio.REST.PageTwilio.REST.Messaging.V1.DomainConfigContext→Twilio.REST.InstanceContextTwilio.REST.Messaging.V1.DomainConfigInstance→Twilio.REST.InstanceResourceTwilio.REST.Messaging.V1.DomainConfigInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Messaging.V1.DomainConfigList→Twilio.REST.ListResourceTwilio.REST.Messaging.V1.DomainConfigListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Messaging.V1.DomainConfigMessagingServiceContext→Twilio.REST.InstanceContext
- Direction
- REST.Messaging.V1 uses REST, so a change to REST can break REST.Messaging.V1, while a change to REST.Messaging.V1 can't break REST.
- Position
- Below the diagonal: REST.Messaging.V1 uses a module listed above it, which is the healthy direction.
22→2 REST.Preview.Marketplace uses REST✕
- Connections
- 14 pairs of types, where a type in REST.Preview.Marketplace uses a type in REST.
- The types involved
Twilio.REST.Preview.Marketplace.AvailableAddOnContext→Twilio.REST.InstanceContextTwilio.REST.Preview.Marketplace.AvailableAddOnInstance→Twilio.REST.InstanceResourceTwilio.REST.Preview.Marketplace.AvailableAddOnInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Preview.Marketplace.AvailableAddOnList→Twilio.REST.ListResourceTwilio.REST.Preview.Marketplace.AvailableAddOnListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Preview.Marketplace.AvailableAddOnPage→Twilio.REST.PageTwilio.REST.Preview.Marketplace.AvailableAddOnPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Preview.Marketplace.InstalledAddOnContext→Twilio.REST.InstanceContextTwilio.REST.Preview.Marketplace.InstalledAddOnInstance→Twilio.REST.InstanceResourceTwilio.REST.Preview.Marketplace.InstalledAddOnInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Preview.Marketplace.InstalledAddOnList→Twilio.REST.ListResourceTwilio.REST.Preview.Marketplace.InstalledAddOnListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Preview.Marketplace.InstalledAddOnPage→Twilio.REST.PageTwilio.REST.Preview.Marketplace.InstalledAddOnPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Preview.Marketplace uses REST, so a change to REST can break REST.Preview.Marketplace, while a change to REST.Preview.Marketplace can't break REST.
- Position
- Below the diagonal: REST.Preview.Marketplace uses a module listed above it, which is the healthy direction.
23→2 REST.Proxy.V1.ServiceContext.SessionContext uses REST✕
- Connections
- 14 pairs of types, where a type in REST.Proxy.V1.ServiceContext.SessionContext uses a type in REST.
- The types involved
Twilio.REST.Proxy.V1.ServiceContext.SessionContext.InteractionContext→Twilio.REST.InstanceContextTwilio.REST.Proxy.V1.ServiceContext.SessionContext.InteractionInstance→Twilio.REST.InstanceResourceTwilio.REST.Proxy.V1.ServiceContext.SessionContext.InteractionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Proxy.V1.ServiceContext.SessionContext.InteractionList→Twilio.REST.ListResourceTwilio.REST.Proxy.V1.ServiceContext.SessionContext.InteractionListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Proxy.V1.ServiceContext.SessionContext.InteractionPage→Twilio.REST.PageTwilio.REST.Proxy.V1.ServiceContext.SessionContext.InteractionPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Proxy.V1.ServiceContext.SessionContext.ParticipantContext→Twilio.REST.InstanceContextTwilio.REST.Proxy.V1.ServiceContext.SessionContext.ParticipantInstance→Twilio.REST.InstanceResourceTwilio.REST.Proxy.V1.ServiceContext.SessionContext.ParticipantInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Proxy.V1.ServiceContext.SessionContext.ParticipantList→Twilio.REST.ListResourceTwilio.REST.Proxy.V1.ServiceContext.SessionContext.ParticipantListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Proxy.V1.ServiceContext.SessionContext.ParticipantPage→Twilio.REST.PageTwilio.REST.Proxy.V1.ServiceContext.SessionContext.ParticipantPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Proxy.V1.ServiceContext.SessionContext uses REST, so a change to REST can break REST.Proxy.V1.ServiceContext.SessionContext, while a change to REST.Proxy.V1.ServiceContext.SessionContext can't break REST.
- Position
- Below the diagonal: REST.Proxy.V1.ServiceContext.SessionContext uses a module listed above it, which is the healthy direction.
24→2 REST.Serverless.V1.ServiceContext uses REST✕
- Connections
- 28 pairs of types, where a type in REST.Serverless.V1.ServiceContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Serverless.V1.ServiceContext.AssetContext→Twilio.REST.InstanceContextTwilio.REST.Serverless.V1.ServiceContext.AssetInstance→Twilio.REST.InstanceResourceTwilio.REST.Serverless.V1.ServiceContext.AssetInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Serverless.V1.ServiceContext.AssetList→Twilio.REST.ListResourceTwilio.REST.Serverless.V1.ServiceContext.AssetListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Serverless.V1.ServiceContext.AssetPage→Twilio.REST.PageTwilio.REST.Serverless.V1.ServiceContext.AssetPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Serverless.V1.ServiceContext.BuildContext→Twilio.REST.InstanceContextTwilio.REST.Serverless.V1.ServiceContext.BuildInstance→Twilio.REST.InstanceResourceTwilio.REST.Serverless.V1.ServiceContext.BuildInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Serverless.V1.ServiceContext.BuildList→Twilio.REST.ListResourceTwilio.REST.Serverless.V1.ServiceContext.BuildListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Serverless.V1.ServiceContext.BuildPage→Twilio.REST.PageTwilio.REST.Serverless.V1.ServiceContext.BuildPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Serverless.V1.ServiceContext.EnvironmentContext→Twilio.REST.InstanceContextTwilio.REST.Serverless.V1.ServiceContext.EnvironmentInstance→Twilio.REST.InstanceResourceTwilio.REST.Serverless.V1.ServiceContext.EnvironmentInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Serverless.V1.ServiceContext.EnvironmentList→Twilio.REST.ListResourceTwilio.REST.Serverless.V1.ServiceContext.EnvironmentListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Serverless.V1.ServiceContext.EnvironmentPage→Twilio.REST.PageTwilio.REST.Serverless.V1.ServiceContext.EnvironmentPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Serverless.V1.ServiceContext.FunctionContext→Twilio.REST.InstanceContextTwilio.REST.Serverless.V1.ServiceContext.FunctionInstance→Twilio.REST.InstanceResourceTwilio.REST.Serverless.V1.ServiceContext.FunctionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Serverless.V1.ServiceContext.FunctionList→Twilio.REST.ListResource
- Direction
- REST.Serverless.V1.ServiceContext uses REST, so a change to REST can break REST.Serverless.V1.ServiceContext, while a change to REST.Serverless.V1.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.Serverless.V1.ServiceContext uses a module listed above it, which is the healthy direction.
25→2 REST.Studio.V1.FlowContext uses REST✕
- Connections
- 14 pairs of types, where a type in REST.Studio.V1.FlowContext uses a type in REST.
- The types involved
Twilio.REST.Studio.V1.FlowContext.EngagementContext→Twilio.REST.InstanceContextTwilio.REST.Studio.V1.FlowContext.EngagementInstance→Twilio.REST.InstanceResourceTwilio.REST.Studio.V1.FlowContext.EngagementInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Studio.V1.FlowContext.EngagementList→Twilio.REST.ListResourceTwilio.REST.Studio.V1.FlowContext.EngagementListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Studio.V1.FlowContext.EngagementPage→Twilio.REST.PageTwilio.REST.Studio.V1.FlowContext.EngagementPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Studio.V1.FlowContext.ExecutionContext→Twilio.REST.InstanceContextTwilio.REST.Studio.V1.FlowContext.ExecutionInstance→Twilio.REST.InstanceResourceTwilio.REST.Studio.V1.FlowContext.ExecutionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Studio.V1.FlowContext.ExecutionList→Twilio.REST.ListResourceTwilio.REST.Studio.V1.FlowContext.ExecutionListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Studio.V1.FlowContext.ExecutionPage→Twilio.REST.PageTwilio.REST.Studio.V1.FlowContext.ExecutionPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Studio.V1.FlowContext uses REST, so a change to REST can break REST.Studio.V1.FlowContext, while a change to REST.Studio.V1.FlowContext can't break REST.
- Position
- Below the diagonal: REST.Studio.V1.FlowContext uses a module listed above it, which is the healthy direction.
26→2 REST.Studio.V2.FlowContext uses REST✕
- Connections
- 20 pairs of types, where a type in REST.Studio.V2.FlowContext uses a type in REST.
- The types involved
Twilio.REST.Studio.V2.FlowContext.ExecutionContext→Twilio.REST.InstanceContextTwilio.REST.Studio.V2.FlowContext.ExecutionInstance→Twilio.REST.InstanceResourceTwilio.REST.Studio.V2.FlowContext.ExecutionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Studio.V2.FlowContext.ExecutionList→Twilio.REST.ListResourceTwilio.REST.Studio.V2.FlowContext.ExecutionListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Studio.V2.FlowContext.ExecutionPage→Twilio.REST.PageTwilio.REST.Studio.V2.FlowContext.ExecutionPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Studio.V2.FlowContext.FlowRevisionContext→Twilio.REST.InstanceContextTwilio.REST.Studio.V2.FlowContext.FlowRevisionInstance→Twilio.REST.InstanceResourceTwilio.REST.Studio.V2.FlowContext.FlowRevisionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Studio.V2.FlowContext.FlowRevisionList→Twilio.REST.ListResourceTwilio.REST.Studio.V2.FlowContext.FlowRevisionListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Studio.V2.FlowContext.FlowRevisionPage→Twilio.REST.PageTwilio.REST.Studio.V2.FlowContext.FlowRevisionPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Studio.V2.FlowContext.FlowTestUserContext→Twilio.REST.InstanceContextTwilio.REST.Studio.V2.FlowContext.FlowTestUserInstance→Twilio.REST.InstanceResourceTwilio.REST.Studio.V2.FlowContext.FlowTestUserInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Studio.V2.FlowContext.FlowTestUserList→Twilio.REST.ListResourceTwilio.REST.Studio.V2.FlowContext.FlowTestUserListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Studio.V2.FlowContext.FlowTestUserPage→Twilio.REST.Page
- Direction
- REST.Studio.V2.FlowContext uses REST, so a change to REST can break REST.Studio.V2.FlowContext, while a change to REST.Studio.V2.FlowContext can't break REST.
- Position
- Below the diagonal: REST.Studio.V2.FlowContext uses a module listed above it, which is the healthy direction.
27→2 REST.Supersim.V1 uses REST✕
- Connections
- 59 pairs of types, where a type in REST.Supersim.V1 uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Supersim.V1.EsimProfileContext→Twilio.REST.InstanceContextTwilio.REST.Supersim.V1.EsimProfileInstance→Twilio.REST.InstanceResourceTwilio.REST.Supersim.V1.EsimProfileInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Supersim.V1.EsimProfileList→Twilio.REST.ListResourceTwilio.REST.Supersim.V1.EsimProfileListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Supersim.V1.EsimProfilePage→Twilio.REST.PageTwilio.REST.Supersim.V1.EsimProfilePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Supersim.V1.FleetContext→Twilio.REST.InstanceContextTwilio.REST.Supersim.V1.FleetInstance→Twilio.REST.InstanceResourceTwilio.REST.Supersim.V1.FleetInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Supersim.V1.FleetList→Twilio.REST.ListResourceTwilio.REST.Supersim.V1.FleetListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Supersim.V1.FleetPage→Twilio.REST.PageTwilio.REST.Supersim.V1.FleetPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Supersim.V1.IpCommandContext→Twilio.REST.InstanceContextTwilio.REST.Supersim.V1.IpCommandInstance→Twilio.REST.InstanceResourceTwilio.REST.Supersim.V1.IpCommandInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Supersim.V1.IpCommandList→Twilio.REST.ListResourceTwilio.REST.Supersim.V1.IpCommandListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Supersim.V1.IpCommandPage→Twilio.REST.PageTwilio.REST.Supersim.V1.IpCommandPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Supersim.V1.NetworkAccessProfileContext→Twilio.REST.InstanceContextTwilio.REST.Supersim.V1.NetworkAccessProfileInstance→Twilio.REST.InstanceResourceTwilio.REST.Supersim.V1.NetworkAccessProfileInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Supersim.V1.NetworkAccessProfileList→Twilio.REST.ListResource
- Direction
- REST.Supersim.V1 uses REST, so a change to REST can break REST.Supersim.V1, while a change to REST.Supersim.V1 can't break REST.
- Position
- Below the diagonal: REST.Supersim.V1 uses a module listed above it, which is the healthy direction.
28→2 REST.Sync.V1.ServiceContext uses REST✕
- Connections
- 28 pairs of types, where a type in REST.Sync.V1.ServiceContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Sync.V1.ServiceContext.DocumentContext→Twilio.REST.InstanceContextTwilio.REST.Sync.V1.ServiceContext.DocumentInstance→Twilio.REST.InstanceResourceTwilio.REST.Sync.V1.ServiceContext.DocumentInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Sync.V1.ServiceContext.DocumentList→Twilio.REST.ListResourceTwilio.REST.Sync.V1.ServiceContext.DocumentListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Sync.V1.ServiceContext.DocumentPage→Twilio.REST.PageTwilio.REST.Sync.V1.ServiceContext.DocumentPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Sync.V1.ServiceContext.SyncListContext→Twilio.REST.InstanceContextTwilio.REST.Sync.V1.ServiceContext.SyncListInstance→Twilio.REST.InstanceResourceTwilio.REST.Sync.V1.ServiceContext.SyncListInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Sync.V1.ServiceContext.SyncListList→Twilio.REST.ListResourceTwilio.REST.Sync.V1.ServiceContext.SyncListListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Sync.V1.ServiceContext.SyncListPage→Twilio.REST.PageTwilio.REST.Sync.V1.ServiceContext.SyncListPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Sync.V1.ServiceContext.SyncMapContext→Twilio.REST.InstanceContextTwilio.REST.Sync.V1.ServiceContext.SyncMapInstance→Twilio.REST.InstanceResourceTwilio.REST.Sync.V1.ServiceContext.SyncMapInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Sync.V1.ServiceContext.SyncMapList→Twilio.REST.ListResourceTwilio.REST.Sync.V1.ServiceContext.SyncMapListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Sync.V1.ServiceContext.SyncMapPage→Twilio.REST.PageTwilio.REST.Sync.V1.ServiceContext.SyncMapPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Sync.V1.ServiceContext.SyncStreamContext→Twilio.REST.InstanceContextTwilio.REST.Sync.V1.ServiceContext.SyncStreamInstance→Twilio.REST.InstanceResourceTwilio.REST.Sync.V1.ServiceContext.SyncStreamInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Sync.V1.ServiceContext.SyncStreamList→Twilio.REST.ListResource
- Direction
- REST.Sync.V1.ServiceContext uses REST, so a change to REST can break REST.Sync.V1.ServiceContext, while a change to REST.Sync.V1.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.Sync.V1.ServiceContext uses a module listed above it, which is the healthy direction.
29→2 REST.Taskrouter.V1.WorkspaceContext uses REST✕
- Connections
- 67 pairs of types, where a type in REST.Taskrouter.V1.WorkspaceContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Taskrouter.V1.WorkspaceContext.ActivityContext→Twilio.REST.InstanceContextTwilio.REST.Taskrouter.V1.WorkspaceContext.ActivityInstance→Twilio.REST.InstanceResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.ActivityInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Taskrouter.V1.WorkspaceContext.ActivityList→Twilio.REST.ListResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.ActivityListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.ActivityPage→Twilio.REST.PageTwilio.REST.Taskrouter.V1.WorkspaceContext.ActivityPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Taskrouter.V1.WorkspaceContext.EventContext→Twilio.REST.InstanceContextTwilio.REST.Taskrouter.V1.WorkspaceContext.EventInstance→Twilio.REST.InstanceResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.EventInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Taskrouter.V1.WorkspaceContext.EventList→Twilio.REST.ListResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.EventListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.EventPage→Twilio.REST.PageTwilio.REST.Taskrouter.V1.WorkspaceContext.EventPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskChannelContext→Twilio.REST.InstanceContextTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskChannelInstance→Twilio.REST.InstanceResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskChannelInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskChannelList→Twilio.REST.ListResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskChannelListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskChannelPage→Twilio.REST.PageTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskChannelPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskContext→Twilio.REST.InstanceContextTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskInstance→Twilio.REST.InstanceResourceTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Taskrouter.V1.WorkspaceContext.TaskList→Twilio.REST.ListResource
- Direction
- REST.Taskrouter.V1.WorkspaceContext uses REST, so a change to REST can break REST.Taskrouter.V1.WorkspaceContext, while a change to REST.Taskrouter.V1.WorkspaceContext can't break REST.
- Position
- Below the diagonal: REST.Taskrouter.V1.WorkspaceContext uses a module listed above it, which is the healthy direction.
30→2 REST.Trusthub.V1 uses REST✕
- Connections
- 88 pairs of types, where a type in REST.Trusthub.V1 uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Trusthub.V1.A2PBrandRegistrationEmbeddedSessionInstance→Twilio.REST.InstanceResourceTwilio.REST.Trusthub.V1.A2PBrandRegistrationEmbeddedSessionList→Twilio.REST.ListResourceTwilio.REST.Trusthub.V1.A2PBrandRegistrationEmbeddedSessionPage→Twilio.REST.PageTwilio.REST.Trusthub.V1.A2PBrandRegistrationInstance→Twilio.REST.InstanceResourceTwilio.REST.Trusthub.V1.A2PBrandRegistrationList→Twilio.REST.ListResourceTwilio.REST.Trusthub.V1.A2PBrandRegistrationPage→Twilio.REST.PageTwilio.REST.Trusthub.V1.A2PCampaignRegistrationEmbeddedSessionInstance→Twilio.REST.InstanceResourceTwilio.REST.Trusthub.V1.A2PCampaignRegistrationEmbeddedSessionList→Twilio.REST.ListResourceTwilio.REST.Trusthub.V1.A2PCampaignRegistrationEmbeddedSessionPage→Twilio.REST.PageTwilio.REST.Trusthub.V1.A2PCampaignRegistrationInstance→Twilio.REST.InstanceResourceTwilio.REST.Trusthub.V1.A2PCampaignRegistrationList→Twilio.REST.ListResourceTwilio.REST.Trusthub.V1.A2PCampaignRegistrationPage→Twilio.REST.PageTwilio.REST.Trusthub.V1.ComplianceInquiriesContext→Twilio.REST.InstanceContextTwilio.REST.Trusthub.V1.ComplianceInquiriesInstance→Twilio.REST.InstanceResourceTwilio.REST.Trusthub.V1.ComplianceInquiriesInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Trusthub.V1.ComplianceInquiriesList→Twilio.REST.ListResourceTwilio.REST.Trusthub.V1.ComplianceInquiriesListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Trusthub.V1.ComplianceInquiriesPage→Twilio.REST.PageTwilio.REST.Trusthub.V1.ComplianceRegistrationInquiriesContext→Twilio.REST.InstanceContextTwilio.REST.Trusthub.V1.ComplianceRegistrationInquiriesInstance→Twilio.REST.InstanceResourceTwilio.REST.Trusthub.V1.ComplianceRegistrationInquiriesInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Trusthub.V1.ComplianceRegistrationInquiriesList→Twilio.REST.ListResourceTwilio.REST.Trusthub.V1.ComplianceRegistrationInquiriesListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Trusthub.V1.ComplianceRegistrationInquiriesPage→Twilio.REST.PageTwilio.REST.Trusthub.V1.ComplianceTollfreeInquiriesInstance→Twilio.REST.InstanceResource
- Direction
- REST.Trusthub.V1 uses REST, so a change to REST can break REST.Trusthub.V1, while a change to REST.Trusthub.V1 can't break REST.
- Position
- Below the diagonal: REST.Trusthub.V1 uses a module listed above it, which is the healthy direction.
31→2 REST.Verify.V2.ServiceContext.EntityContext uses REST✕
- Connections
- 17 pairs of types, where a type in REST.Verify.V2.ServiceContext.EntityContext uses a type in REST.
- The types involved
Twilio.REST.Verify.V2.ServiceContext.EntityContext.ChallengeContext→Twilio.REST.InstanceContextTwilio.REST.Verify.V2.ServiceContext.EntityContext.ChallengeInstance→Twilio.REST.InstanceResourceTwilio.REST.Verify.V2.ServiceContext.EntityContext.ChallengeInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Verify.V2.ServiceContext.EntityContext.ChallengeList→Twilio.REST.ListResourceTwilio.REST.Verify.V2.ServiceContext.EntityContext.ChallengeListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Verify.V2.ServiceContext.EntityContext.ChallengePage→Twilio.REST.PageTwilio.REST.Verify.V2.ServiceContext.EntityContext.ChallengePageMetadata→Twilio.REST.PageMetadataTwilio.REST.Verify.V2.ServiceContext.EntityContext.FactorContext→Twilio.REST.InstanceContextTwilio.REST.Verify.V2.ServiceContext.EntityContext.FactorInstance→Twilio.REST.InstanceResourceTwilio.REST.Verify.V2.ServiceContext.EntityContext.FactorInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Verify.V2.ServiceContext.EntityContext.FactorList→Twilio.REST.ListResourceTwilio.REST.Verify.V2.ServiceContext.EntityContext.FactorListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Verify.V2.ServiceContext.EntityContext.FactorPage→Twilio.REST.PageTwilio.REST.Verify.V2.ServiceContext.EntityContext.FactorPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Verify.V2.ServiceContext.EntityContext.NewFactorInstance→Twilio.REST.InstanceResourceTwilio.REST.Verify.V2.ServiceContext.EntityContext.NewFactorList→Twilio.REST.ListResourceTwilio.REST.Verify.V2.ServiceContext.EntityContext.NewFactorPage→Twilio.REST.Page
- Direction
- REST.Verify.V2.ServiceContext.EntityContext uses REST, so a change to REST can break REST.Verify.V2.ServiceContext.EntityContext, while a change to REST.Verify.V2.ServiceContext.EntityContext can't break REST.
- Position
- Below the diagonal: REST.Verify.V2.ServiceContext.EntityContext uses a module listed above it, which is the healthy direction.
32→2 REST.Video.V1.RoomContext uses REST✕
- Connections
- 24 pairs of types, where a type in REST.Video.V1.RoomContext uses a type in REST.
- The types involved
Twilio.REST.Video.V1.RoomContext.ParticipantContext→Twilio.REST.InstanceContextTwilio.REST.Video.V1.RoomContext.ParticipantInstance→Twilio.REST.InstanceResourceTwilio.REST.Video.V1.RoomContext.ParticipantInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Video.V1.RoomContext.ParticipantList→Twilio.REST.ListResourceTwilio.REST.Video.V1.RoomContext.ParticipantListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Video.V1.RoomContext.ParticipantPage→Twilio.REST.PageTwilio.REST.Video.V1.RoomContext.ParticipantPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Video.V1.RoomContext.RecordingRulesInstance→Twilio.REST.InstanceResourceTwilio.REST.Video.V1.RoomContext.RecordingRulesList→Twilio.REST.ListResourceTwilio.REST.Video.V1.RoomContext.RecordingRulesPage→Twilio.REST.PageTwilio.REST.Video.V1.RoomContext.RoomRecordingContext→Twilio.REST.InstanceContextTwilio.REST.Video.V1.RoomContext.RoomRecordingInstance→Twilio.REST.InstanceResourceTwilio.REST.Video.V1.RoomContext.RoomRecordingInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Video.V1.RoomContext.RoomRecordingList→Twilio.REST.ListResourceTwilio.REST.Video.V1.RoomContext.RoomRecordingListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Video.V1.RoomContext.RoomRecordingPage→Twilio.REST.PageTwilio.REST.Video.V1.RoomContext.RoomRecordingPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Video.V1.RoomContext.TranscriptionsContext→Twilio.REST.InstanceContextTwilio.REST.Video.V1.RoomContext.TranscriptionsInstance→Twilio.REST.InstanceResourceTwilio.REST.Video.V1.RoomContext.TranscriptionsInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Video.V1.RoomContext.TranscriptionsList→Twilio.REST.ListResourceTwilio.REST.Video.V1.RoomContext.TranscriptionsListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Video.V1.RoomContext.TranscriptionsPage→Twilio.REST.PageTwilio.REST.Video.V1.RoomContext.TranscriptionsPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Video.V1.RoomContext uses REST, so a change to REST can break REST.Video.V1.RoomContext, while a change to REST.Video.V1.RoomContext can't break REST.
- Position
- Below the diagonal: REST.Video.V1.RoomContext uses a module listed above it, which is the healthy direction.
33→2 REST.Api.V2010.AccountContext.IncomingPhoneNumberContext uses REST✕
- Connections
- 7 pairs of types, where a type in REST.Api.V2010.AccountContext.IncomingPhoneNumberContext uses a type in REST.
- The types involved
Twilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010.AccountContext.IncomingPhoneNumberContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext.IncomingPhoneNumberContext, while a change to REST.Api.V2010.AccountContext.IncomingPhoneNumberContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.IncomingPhoneNumberContext uses a module listed above it, which is the healthy direction.
33→7 REST.Api.V2010.AccountContext.IncomingPhoneNumberContext uses REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext✕
- Connections
- 1 pair of types, where a type in REST.Api.V2010.AccountContext.IncomingPhoneNumberContext uses a type in REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext→Twilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.AssignedAddOnExtensionList
- Direction
- REST.Api.V2010.AccountContext.IncomingPhoneNumberContext uses REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext, so a change to REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext can break REST.Api.V2010.AccountContext.IncomingPhoneNumberContext, while a change to REST.Api.V2010.AccountContext.IncomingPhoneNumberContext can't break REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnContext.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext.IncomingPhoneNumberContext uses a module listed above it, which is the healthy direction.
34→2 REST.Conversations.V1.ServiceContext uses REST✕
- Connections
- 42 pairs of types, where a type in REST.Conversations.V1.ServiceContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Conversations.V1.ServiceContext.BindingContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ServiceContext.BindingInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ServiceContext.BindingInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ServiceContext.BindingList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ServiceContext.BindingListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ServiceContext.BindingPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ServiceContext.BindingPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Conversations.V1.ServiceContext.ConfigurationContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ServiceContext.ConfigurationInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ServiceContext.ConfigurationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ServiceContext.ConfigurationList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ServiceContext.ConfigurationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ServiceContext.ConfigurationPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ServiceContext.ConversationContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ServiceContext.ConversationInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ServiceContext.ConversationList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ServiceContext.ConversationPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Conversations.V1.ServiceContext.ConversationWithParticipantsInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationWithParticipantsList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ServiceContext.ConversationWithParticipantsPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ServiceContext.ParticipantConversationInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ServiceContext.ParticipantConversationList→Twilio.REST.ListResource
- Direction
- REST.Conversations.V1.ServiceContext uses REST, so a change to REST can break REST.Conversations.V1.ServiceContext, while a change to REST.Conversations.V1.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.Conversations.V1.ServiceContext uses a module listed above it, which is the healthy direction.
34→14 REST.Conversations.V1.ServiceContext uses REST.Conversations.V1.ServiceContext.ConversationContext✕
- Connections
- 3 pairs of types, where a type in REST.Conversations.V1.ServiceContext uses a type in REST.Conversations.V1.ServiceContext.ConversationContext.
- The types involved
Twilio.REST.Conversations.V1.ServiceContext.ConversationContext→Twilio.REST.Conversations.V1.ServiceContext.ConversationContext.MessageListTwilio.REST.Conversations.V1.ServiceContext.ConversationContext→Twilio.REST.Conversations.V1.ServiceContext.ConversationContext.ParticipantListTwilio.REST.Conversations.V1.ServiceContext.ConversationContext→Twilio.REST.Conversations.V1.ServiceContext.ConversationContext.WebhookList
- Direction
- REST.Conversations.V1.ServiceContext uses REST.Conversations.V1.ServiceContext.ConversationContext, so a change to REST.Conversations.V1.ServiceContext.ConversationContext can break REST.Conversations.V1.ServiceContext, while a change to REST.Conversations.V1.ServiceContext can't break REST.Conversations.V1.ServiceContext.ConversationContext.
- Position
- Below the diagonal: REST.Conversations.V1.ServiceContext uses a module listed above it, which is the healthy direction.
35→2 REST.FlexApi.V1 uses REST✕
- Connections
- 139 pairs of types, where a type in REST.FlexApi.V1 uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.FlexApi.V1.AssessmentsContext→Twilio.REST.InstanceContextTwilio.REST.FlexApi.V1.AssessmentsInstance→Twilio.REST.InstanceResourceTwilio.REST.FlexApi.V1.AssessmentsInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.FlexApi.V1.AssessmentsList→Twilio.REST.ListResourceTwilio.REST.FlexApi.V1.AssessmentsListResponse→Twilio.REST.InstanceListResourceTwilio.REST.FlexApi.V1.AssessmentsPage→Twilio.REST.PageTwilio.REST.FlexApi.V1.AssessmentsPageMetadata→Twilio.REST.PageMetadataTwilio.REST.FlexApi.V1.ChannelContext→Twilio.REST.InstanceContextTwilio.REST.FlexApi.V1.ChannelInstance→Twilio.REST.InstanceResourceTwilio.REST.FlexApi.V1.ChannelInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.FlexApi.V1.ChannelList→Twilio.REST.ListResourceTwilio.REST.FlexApi.V1.ChannelListResponse→Twilio.REST.InstanceListResourceTwilio.REST.FlexApi.V1.ChannelPage→Twilio.REST.PageTwilio.REST.FlexApi.V1.ChannelPageMetadata→Twilio.REST.PageMetadataTwilio.REST.FlexApi.V1.ConfigurationContext→Twilio.REST.InstanceContextTwilio.REST.FlexApi.V1.ConfigurationInstance→Twilio.REST.InstanceResourceTwilio.REST.FlexApi.V1.ConfigurationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.FlexApi.V1.ConfigurationList→Twilio.REST.ListResourceTwilio.REST.FlexApi.V1.ConfigurationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.FlexApi.V1.ConfigurationPage→Twilio.REST.PageTwilio.REST.FlexApi.V1.FlexFlowContext→Twilio.REST.InstanceContextTwilio.REST.FlexApi.V1.FlexFlowInstance→Twilio.REST.InstanceResourceTwilio.REST.FlexApi.V1.FlexFlowInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.FlexApi.V1.FlexFlowList→Twilio.REST.ListResourceTwilio.REST.FlexApi.V1.FlexFlowListResponse→Twilio.REST.InstanceListResource
- Direction
- REST.FlexApi.V1 uses REST, so a change to REST can break REST.FlexApi.V1, while a change to REST.FlexApi.V1 can't break REST.
- Position
- Below the diagonal: REST.FlexApi.V1 uses a module listed above it, which is the healthy direction.
35→16 REST.FlexApi.V1 uses REST.FlexApi.V1.InteractionContext✕
- Connections
- 1 pair of types, where a type in REST.FlexApi.V1 uses a type in REST.FlexApi.V1.InteractionContext.
- The types involved
Twilio.REST.FlexApi.V1.InteractionContext→Twilio.REST.FlexApi.V1.InteractionContext.InteractionChannelList
- Direction
- REST.FlexApi.V1 uses REST.FlexApi.V1.InteractionContext, so a change to REST.FlexApi.V1.InteractionContext can break REST.FlexApi.V1, while a change to REST.FlexApi.V1 can't break REST.FlexApi.V1.InteractionContext.
- Position
- Below the diagonal: REST.FlexApi.V1 uses a module listed above it, which is the healthy direction.
36→2 REST.Proxy.V1.ServiceContext uses REST✕
- Connections
- 14 pairs of types, where a type in REST.Proxy.V1.ServiceContext uses a type in REST.
- The types involved
Twilio.REST.Proxy.V1.ServiceContext.PhoneNumberContext→Twilio.REST.InstanceContextTwilio.REST.Proxy.V1.ServiceContext.PhoneNumberInstance→Twilio.REST.InstanceResourceTwilio.REST.Proxy.V1.ServiceContext.PhoneNumberInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Proxy.V1.ServiceContext.PhoneNumberList→Twilio.REST.ListResourceTwilio.REST.Proxy.V1.ServiceContext.PhoneNumberListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Proxy.V1.ServiceContext.PhoneNumberPage→Twilio.REST.PageTwilio.REST.Proxy.V1.ServiceContext.PhoneNumberPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Proxy.V1.ServiceContext.SessionContext→Twilio.REST.InstanceContextTwilio.REST.Proxy.V1.ServiceContext.SessionInstance→Twilio.REST.InstanceResourceTwilio.REST.Proxy.V1.ServiceContext.SessionInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Proxy.V1.ServiceContext.SessionList→Twilio.REST.ListResourceTwilio.REST.Proxy.V1.ServiceContext.SessionListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Proxy.V1.ServiceContext.SessionPage→Twilio.REST.PageTwilio.REST.Proxy.V1.ServiceContext.SessionPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Proxy.V1.ServiceContext uses REST, so a change to REST can break REST.Proxy.V1.ServiceContext, while a change to REST.Proxy.V1.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.Proxy.V1.ServiceContext uses a module listed above it, which is the healthy direction.
36→23 REST.Proxy.V1.ServiceContext uses REST.Proxy.V1.ServiceContext.SessionContext✕
- Connections
- 2 pairs of types, where a type in REST.Proxy.V1.ServiceContext uses a type in REST.Proxy.V1.ServiceContext.SessionContext.
- The types involved
Twilio.REST.Proxy.V1.ServiceContext.SessionContext→Twilio.REST.Proxy.V1.ServiceContext.SessionContext.InteractionListTwilio.REST.Proxy.V1.ServiceContext.SessionContext→Twilio.REST.Proxy.V1.ServiceContext.SessionContext.ParticipantList
- Direction
- REST.Proxy.V1.ServiceContext uses REST.Proxy.V1.ServiceContext.SessionContext, so a change to REST.Proxy.V1.ServiceContext.SessionContext can break REST.Proxy.V1.ServiceContext, while a change to REST.Proxy.V1.ServiceContext can't break REST.Proxy.V1.ServiceContext.SessionContext.
- Position
- Below the diagonal: REST.Proxy.V1.ServiceContext uses a module listed above it, which is the healthy direction.
37→2 REST.Verify.V2.ServiceContext uses REST✕
- Connections
- 58 pairs of types, where a type in REST.Verify.V2.ServiceContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Verify.V2.ServiceContext.AccessTokenContext→Twilio.REST.InstanceContextTwilio.REST.Verify.V2.ServiceContext.AccessTokenInstance→Twilio.REST.InstanceResourceTwilio.REST.Verify.V2.ServiceContext.AccessTokenInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Verify.V2.ServiceContext.AccessTokenList→Twilio.REST.ListResourceTwilio.REST.Verify.V2.ServiceContext.AccessTokenListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Verify.V2.ServiceContext.AccessTokenPage→Twilio.REST.PageTwilio.REST.Verify.V2.ServiceContext.ApproveChallengeInstance→Twilio.REST.InstanceResourceTwilio.REST.Verify.V2.ServiceContext.ApproveChallengeList→Twilio.REST.ListResourceTwilio.REST.Verify.V2.ServiceContext.ApproveChallengePage→Twilio.REST.PageTwilio.REST.Verify.V2.ServiceContext.EntityContext→Twilio.REST.InstanceContextTwilio.REST.Verify.V2.ServiceContext.EntityInstance→Twilio.REST.InstanceResourceTwilio.REST.Verify.V2.ServiceContext.EntityInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Verify.V2.ServiceContext.EntityList→Twilio.REST.ListResourceTwilio.REST.Verify.V2.ServiceContext.EntityListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Verify.V2.ServiceContext.EntityPage→Twilio.REST.PageTwilio.REST.Verify.V2.ServiceContext.EntityPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Verify.V2.ServiceContext.MessagingConfigurationContext→Twilio.REST.InstanceContextTwilio.REST.Verify.V2.ServiceContext.MessagingConfigurationInstance→Twilio.REST.InstanceResourceTwilio.REST.Verify.V2.ServiceContext.MessagingConfigurationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Verify.V2.ServiceContext.MessagingConfigurationList→Twilio.REST.ListResourceTwilio.REST.Verify.V2.ServiceContext.MessagingConfigurationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Verify.V2.ServiceContext.MessagingConfigurationPage→Twilio.REST.PageTwilio.REST.Verify.V2.ServiceContext.MessagingConfigurationPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Verify.V2.ServiceContext.NewChallengeContext→Twilio.REST.InstanceContextTwilio.REST.Verify.V2.ServiceContext.NewChallengeInstance→Twilio.REST.InstanceResource
- Direction
- REST.Verify.V2.ServiceContext uses REST, so a change to REST can break REST.Verify.V2.ServiceContext, while a change to REST.Verify.V2.ServiceContext can't break REST.
- Position
- Below the diagonal: REST.Verify.V2.ServiceContext uses a module listed above it, which is the healthy direction.
37→31 REST.Verify.V2.ServiceContext uses REST.Verify.V2.ServiceContext.EntityContext✕
- Connections
- 3 pairs of types, where a type in REST.Verify.V2.ServiceContext uses a type in REST.Verify.V2.ServiceContext.EntityContext.
- The types involved
Twilio.REST.Verify.V2.ServiceContext.EntityContext→Twilio.REST.Verify.V2.ServiceContext.EntityContext.ChallengeListTwilio.REST.Verify.V2.ServiceContext.EntityContext→Twilio.REST.Verify.V2.ServiceContext.EntityContext.FactorListTwilio.REST.Verify.V2.ServiceContext.EntityContext→Twilio.REST.Verify.V2.ServiceContext.EntityContext.NewFactorList
- Direction
- REST.Verify.V2.ServiceContext uses REST.Verify.V2.ServiceContext.EntityContext, so a change to REST.Verify.V2.ServiceContext.EntityContext can break REST.Verify.V2.ServiceContext, while a change to REST.Verify.V2.ServiceContext can't break REST.Verify.V2.ServiceContext.EntityContext.
- Position
- Below the diagonal: REST.Verify.V2.ServiceContext uses a module listed above it, which is the healthy direction.
38→2 REST.Api.V2010.AccountContext uses REST✕
- Connections
- 140 pairs of types, where a type in REST.Api.V2010.AccountContext uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Api.V2010.AccountContext.AddressContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.AddressInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AddressInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.AddressList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.AddressListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.AddressPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.AddressPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.ApplicationContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.ApplicationInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.ApplicationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.ApplicationList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.ApplicationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.ApplicationPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.ApplicationPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.AuthorizedConnectAppContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.AuthorizedConnectAppInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AuthorizedConnectAppInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.AuthorizedConnectAppList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountContext.AuthorizedConnectAppListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountContext.AuthorizedConnectAppPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountContext.AuthorizedConnectAppPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryList→Twilio.REST.ListResource
- Direction
- REST.Api.V2010.AccountContext uses REST, so a change to REST can break REST.Api.V2010.AccountContext, while a change to REST.Api.V2010.AccountContext can't break REST.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext uses a module listed above it, which is the healthy direction.
38→3 REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.AddressContext✕
- Connections
- 1 pair of types, where a type in REST.Api.V2010.AccountContext uses a type in REST.Api.V2010.AccountContext.AddressContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext.AddressContext→Twilio.REST.Api.V2010.AccountContext.AddressContext.DependentPhoneNumberList
- Direction
- REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.AddressContext, so a change to REST.Api.V2010.AccountContext.AddressContext can break REST.Api.V2010.AccountContext, while a change to REST.Api.V2010.AccountContext can't break REST.Api.V2010.AccountContext.AddressContext.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext uses a module listed above it, which is the healthy direction.
38→4 REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext✕
- Connections
- 7 pairs of types, where a type in REST.Api.V2010.AccountContext uses a type in REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext→Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.LocalListTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext→Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MachineToMachineListTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext→Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.MobileListTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext→Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.NationalListTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext→Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.SharedCostListTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext→Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.TollFreeListTwilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext→Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.VoipList
- Direction
- REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext, so a change to REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext can break REST.Api.V2010.AccountContext, while a change to REST.Api.V2010.AccountContext can't break REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryContext.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext uses a module listed above it, which is the healthy direction.
38→5 REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.CallContext✕
- Connections
- 9 pairs of types, where a type in REST.Api.V2010.AccountContext uses a type in REST.Api.V2010.AccountContext.CallContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.EventListTwilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.NotificationListTwilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.PaymentListTwilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.RecordingListTwilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.SiprecListTwilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.StreamListTwilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.TranscriptionListTwilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.UserDefinedMessageListTwilio.REST.Api.V2010.AccountContext.CallContext→Twilio.REST.Api.V2010.AccountContext.CallContext.UserDefinedMessageSubscriptionList
- Direction
- REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.CallContext, so a change to REST.Api.V2010.AccountContext.CallContext can break REST.Api.V2010.AccountContext, while a change to REST.Api.V2010.AccountContext can't break REST.Api.V2010.AccountContext.CallContext.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext uses a module listed above it, which is the healthy direction.
38→6 REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.ConferenceContext✕
- Connections
- 2 pairs of types, where a type in REST.Api.V2010.AccountContext uses a type in REST.Api.V2010.AccountContext.ConferenceContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext.ConferenceContext→Twilio.REST.Api.V2010.AccountContext.ConferenceContext.ParticipantListTwilio.REST.Api.V2010.AccountContext.ConferenceContext→Twilio.REST.Api.V2010.AccountContext.ConferenceContext.RecordingList
- Direction
- REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.ConferenceContext, so a change to REST.Api.V2010.AccountContext.ConferenceContext can break REST.Api.V2010.AccountContext, while a change to REST.Api.V2010.AccountContext can't break REST.Api.V2010.AccountContext.ConferenceContext.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext uses a module listed above it, which is the healthy direction.
38→8 REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.MessageContext✕
- Connections
- 2 pairs of types, where a type in REST.Api.V2010.AccountContext uses a type in REST.Api.V2010.AccountContext.MessageContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext.MessageContext→Twilio.REST.Api.V2010.AccountContext.MessageContext.FeedbackListTwilio.REST.Api.V2010.AccountContext.MessageContext→Twilio.REST.Api.V2010.AccountContext.MessageContext.MediaList
- Direction
- REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.MessageContext, so a change to REST.Api.V2010.AccountContext.MessageContext can break REST.Api.V2010.AccountContext, while a change to REST.Api.V2010.AccountContext can't break REST.Api.V2010.AccountContext.MessageContext.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext uses a module listed above it, which is the healthy direction.
38→9 REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.RecordingContext✕
- Connections
- 2 pairs of types, where a type in REST.Api.V2010.AccountContext uses a type in REST.Api.V2010.AccountContext.RecordingContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext.RecordingContext→Twilio.REST.Api.V2010.AccountContext.RecordingContext.AddOnResultListTwilio.REST.Api.V2010.AccountContext.RecordingContext→Twilio.REST.Api.V2010.AccountContext.RecordingContext.TranscriptionList
- Direction
- REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.RecordingContext, so a change to REST.Api.V2010.AccountContext.RecordingContext can break REST.Api.V2010.AccountContext, while a change to REST.Api.V2010.AccountContext can't break REST.Api.V2010.AccountContext.RecordingContext.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext uses a module listed above it, which is the healthy direction.
38→33 REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.IncomingPhoneNumberContext✕
- Connections
- 1 pair of types, where a type in REST.Api.V2010.AccountContext uses a type in REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext→Twilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.AssignedAddOnList
- Direction
- REST.Api.V2010.AccountContext uses REST.Api.V2010.AccountContext.IncomingPhoneNumberContext, so a change to REST.Api.V2010.AccountContext.IncomingPhoneNumberContext can break REST.Api.V2010.AccountContext, while a change to REST.Api.V2010.AccountContext can't break REST.Api.V2010.AccountContext.IncomingPhoneNumberContext.
- Position
- Below the diagonal: REST.Api.V2010.AccountContext uses a module listed above it, which is the healthy direction.
39→2 REST.Conversations.V1 uses REST✕
- Connections
- 56 pairs of types, where a type in REST.Conversations.V1 uses a type in REST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Twilio.REST.Conversations.V1.AddressConfigurationContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.AddressConfigurationInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.AddressConfigurationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.AddressConfigurationList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.AddressConfigurationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.AddressConfigurationPage→Twilio.REST.PageTwilio.REST.Conversations.V1.AddressConfigurationPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Conversations.V1.ConfigurationContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ConfigurationInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ConfigurationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ConfigurationList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ConfigurationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ConfigurationPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ConversationContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.ConversationInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ConversationInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Conversations.V1.ConversationList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ConversationListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Conversations.V1.ConversationPage→Twilio.REST.PageTwilio.REST.Conversations.V1.ConversationPageMetadata→Twilio.REST.PageMetadataTwilio.REST.Conversations.V1.ConversationWithParticipantsInstance→Twilio.REST.InstanceResourceTwilio.REST.Conversations.V1.ConversationWithParticipantsList→Twilio.REST.ListResourceTwilio.REST.Conversations.V1.ConversationWithParticipantsPage→Twilio.REST.PageTwilio.REST.Conversations.V1.CredentialContext→Twilio.REST.InstanceContextTwilio.REST.Conversations.V1.CredentialInstance→Twilio.REST.InstanceResource
- Direction
- REST.Conversations.V1 uses REST, so a change to REST can break REST.Conversations.V1, while a change to REST.Conversations.V1 can't break REST.
- Position
- Below the diagonal: REST.Conversations.V1 uses a module listed above it, which is the healthy direction.
39→13 REST.Conversations.V1 uses REST.Conversations.V1.ConversationContext✕
- Connections
- 3 pairs of types, where a type in REST.Conversations.V1 uses a type in REST.Conversations.V1.ConversationContext.
- The types involved
Twilio.REST.Conversations.V1.ConversationContext→Twilio.REST.Conversations.V1.ConversationContext.MessageListTwilio.REST.Conversations.V1.ConversationContext→Twilio.REST.Conversations.V1.ConversationContext.ParticipantListTwilio.REST.Conversations.V1.ConversationContext→Twilio.REST.Conversations.V1.ConversationContext.WebhookList
- Direction
- REST.Conversations.V1 uses REST.Conversations.V1.ConversationContext, so a change to REST.Conversations.V1.ConversationContext can break REST.Conversations.V1, while a change to REST.Conversations.V1 can't break REST.Conversations.V1.ConversationContext.
- Position
- Below the diagonal: REST.Conversations.V1 uses a module listed above it, which is the healthy direction.
39→34 REST.Conversations.V1 uses REST.Conversations.V1.ServiceContext✕
- Connections
- 6 pairs of types, where a type in REST.Conversations.V1 uses a type in REST.Conversations.V1.ServiceContext.
- The types involved
Twilio.REST.Conversations.V1.ServiceContext→Twilio.REST.Conversations.V1.ServiceContext.BindingListTwilio.REST.Conversations.V1.ServiceContext→Twilio.REST.Conversations.V1.ServiceContext.ConversationListTwilio.REST.Conversations.V1.ServiceContext→Twilio.REST.Conversations.V1.ServiceContext.ConversationWithParticipantsListTwilio.REST.Conversations.V1.ServiceContext→Twilio.REST.Conversations.V1.ServiceContext.ParticipantConversationListTwilio.REST.Conversations.V1.ServiceContext→Twilio.REST.Conversations.V1.ServiceContext.RoleListTwilio.REST.Conversations.V1.ServiceContext→Twilio.REST.Conversations.V1.ServiceContext.UserList
- Direction
- REST.Conversations.V1 uses REST.Conversations.V1.ServiceContext, so a change to REST.Conversations.V1.ServiceContext can break REST.Conversations.V1, while a change to REST.Conversations.V1 can't break REST.Conversations.V1.ServiceContext.
- Position
- Below the diagonal: REST.Conversations.V1 uses a module listed above it, which is the healthy direction.
40→2 REST.Api.V2010 uses REST✕
- Connections
- 7 pairs of types, where a type in REST.Api.V2010 uses a type in REST.
- The types involved
Twilio.REST.Api.V2010.AccountContext→Twilio.REST.InstanceContextTwilio.REST.Api.V2010.AccountInstance→Twilio.REST.InstanceResourceTwilio.REST.Api.V2010.AccountInstanceMetadata→Twilio.REST.InstanceResourceMetadataTwilio.REST.Api.V2010.AccountList→Twilio.REST.ListResourceTwilio.REST.Api.V2010.AccountListResponse→Twilio.REST.InstanceListResourceTwilio.REST.Api.V2010.AccountPage→Twilio.REST.PageTwilio.REST.Api.V2010.AccountPageMetadata→Twilio.REST.PageMetadata
- Direction
- REST.Api.V2010 uses REST, so a change to REST can break REST.Api.V2010, while a change to REST.Api.V2010 can't break REST.
- Position
- Below the diagonal: REST.Api.V2010 uses a module listed above it, which is the healthy direction.
40→38 REST.Api.V2010 uses REST.Api.V2010.AccountContext✕
- Connections
- 24 pairs of types, where a type in REST.Api.V2010 uses a type in REST.Api.V2010.AccountContext.
- The types involved
Twilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.AddressListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.ApplicationListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.AuthorizedConnectAppListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.AvailablePhoneNumberCountryListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.BalanceListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.CallListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.ConferenceListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.ConnectAppListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.IncomingPhoneNumberListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.KeyListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.MessageListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.NewKeyListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.NewSigningKeyListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.NotificationListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.OutgoingCallerIdListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.QueueListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.RecordingListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.ShortCodeListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.SigningKeyListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.SipListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.TokenListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.TranscriptionListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.UsageListTwilio.REST.Api.V2010.AccountContext→Twilio.REST.Api.V2010.AccountContext.ValidationRequestList
- Direction
- REST.Api.V2010 uses REST.Api.V2010.AccountContext, so a change to REST.Api.V2010.AccountContext can break REST.Api.V2010, while a change to REST.Api.V2010 can't break REST.Api.V2010.AccountContext.
- Position
- Below the diagonal: REST.Api.V2010 uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A05:2025 — Injection | 7 | High / Critical |
| A07:2025 — Authentication Failures | 4 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with api.rb, task_router.rb, access_token.rb; Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.8 pts | Medium | Architecture documentation |
| Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with api.rb, task_router.rb, access_token.rb. | +4.8 pts | Medium | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing. | +3.2 pts | Medium | Security & performance tooling |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +2.4 pts | Medium | Documentation (README) |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +1.9 pts | Medium | Deployment & Rollback |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.8 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| lib/twilio-ruby/twiml/voice_response.rb | 8.5 | Near-clean | God Classes: FileTooLong: twiml/voice_response.rb |
| lib/twilio-ruby/http/client_token_manager.rb | 8.5 | Near-clean | Code Duplication: Duplicated block (20 lines × 2) |
| lib/twilio-ruby/credential/client_credential_provider.rb | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| lib/twilio-ruby/rest/memory/v1.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: V1 (LCOM4 15) |
| lib/twilio-ruby/rest/flex_api/v1.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: V1 (LCOM4 14) |
| lib/twilio-ruby/rest/trusthub/v1.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: V1 (LCOM4 13) |
| lib/twilio-ruby/rest/messaging/v1.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: V1 (LCOM4 10) |
| lib/twilio-ruby/rest/intelligence/v2.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: V2 (LCOM4 8) |
| lib/twilio-ruby/rest/supersim/v1.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: V1 (LCOM4 7) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 59 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 52 of 69 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rb) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `spec_helper.rb`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `spec_helper.rb`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with voice_response.rb. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with client_token_manager.rb. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with client_credential_provider.rb. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
20 of 1037 classes have LCOM4 above 3.
What to do
- Resolve the 20 Low cohesion finding(s) in Cohesion (LCOM4) — start with v1.rb (11), v2.rb (6), regulatory_compliance.rb. — One of this dimension's main actionable groups (20 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Ruby (RSpec: repository root, 21 spec files): measured (0 flaky).
D12 · Dependency Hygiene
4 outdated direct gem(s), 0 pinning defect(s). 19 declaration(s) graded against rubygems.org, 13 of them against a version resolved in a committed REDACTED. 4 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 28 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 28 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/twilio-ruby/security/request_validator.rb. Counted over 16 of the 80 production source files in this repository: 61 are under the ~2,400-byte size floor this dimension measures over, and the remaining 3 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 5662 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D26 · Project Cohesion
1 of 1 build units (Bundler) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 3 high, 4 medium, 0 low. 1 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 1 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (1 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 1 critical, 0 high, 0 medium, 0 low.
What to do
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
11 of 19 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/twilio-ruby/rest/api.rb. Counted over 19 of the 80 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with api.rb, task_router.rb, access_token.rb. — One of this dimension's main actionable groups (11 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 19 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack as a CI step. What was searched, so you can tell an absence from a miss: the 5279 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
What to do
- Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 80 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
- Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 65% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository draws no route and defines no request handler (no Rails routes.draw or controller, no Sinatra, Roda or Grape application, no Hanami action). Access control is therefore N/A here — a gem is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (an ActiveRecord model, Sequel, pg, mysql2, Mongo) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (ActiveRecord, Sequel, pg, mysql2, mongo, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~3397 lines of test source are present (.rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Ruby not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Ruby surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rb, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this RubyGems build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Ruby source (1 module(s), 80 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Ruby source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `spec_helper.rb`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a Gemfile or gemspec, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Ruby runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
- PF3 Async & latency hygiene — Not applicable: Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 80 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no `config.ru`, no web framework, Rack or server gem among its gemspec run-time dependencies or its Gemfile's production gems, and no Rails, Rack, Sinatra, Grape, Hanami, WEBrick, Puma or Falcon server defined or booted in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby was read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 30 finding(s)
- Low cohesion: V1 (LCOM4 15) lib/twilio-ruby/rest/memory/v1.rb:18
- Low cohesion: V1 (LCOM4 14) lib/twilio-ruby/rest/flex_api/v1.rb:18
- Low cohesion: V1 (LCOM4 13) lib/twilio-ruby/rest/trusthub/v1.rb:18
- Low cohesion: V1 (LCOM4 10) lib/twilio-ruby/rest/messaging/v1.rb:18
- Low cohesion: V2 (LCOM4 8) lib/twilio-ruby/rest/intelligence/v2.rb:18
- Low cohesion: V1 (LCOM4 7) lib/twilio-ruby/rest/supersim/v1.rb:18
- Low cohesion: V1 (LCOM4 6) lib/twilio-ruby/rest/conversations/v1.rb:18
- Low cohesion: V2 (LCOM4 6) lib/twilio-ruby/rest/conversations/v2.rb:18
- Low cohesion: V1 (LCOM4 6) lib/twilio-ruby/rest/numbers/v1.rb:18
- Low cohesion: RegulatoryComplianceList (LCOM4 6) lib/twilio-ruby/rest/numbers/v2/regulatory_compliance.rb:20
- Low cohesion: V3 (LCOM4 5) lib/twilio-ruby/rest/intelligence/v3.rb:18
- Low cohesion: V2 (LCOM4 5) lib/twilio-ruby/rest/knowledge/v2.rb:18
- Low cohesion: V2 (LCOM4 5) lib/twilio-ruby/rest/numbers/v2.rb:18
- Low cohesion: V1 (LCOM4 5) lib/twilio-ruby/rest/voice/v1.rb:18
- Low cohesion: V2 (LCOM4 5) lib/twilio-ruby/rest/voice/v2.rb:18
- Low cohesion: V1 (LCOM4 5) lib/twilio-ruby/rest/webhooks/v1.rb:18
- Low cohesion: V1 (LCOM4 4) lib/twilio-ruby/rest/events/v1.rb:18
- Low cohesion: V2 (LCOM4 4) lib/twilio-ruby/rest/verify/v2.rb:18
- Low cohesion: ServiceContext (LCOM4 4) lib/twilio-ruby/rest/verify/v2/service.rb:367
- Low cohesion: V1 (LCOM4 4) lib/twilio-ruby/rest/video/v1.rb:18
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: twiml/voice_response.rb lib/twilio-ruby/twiml/voice_response.rb
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (20 lines × 2) lib/twilio-ruby/http/client_token_manager.rb:8
- Duplicated block (8 lines × 2) lib/twilio-ruby/credential/client_credential_provider.rb:11
Minor — 27 finding(s)
- Orphaned file lib/twilio-ruby/rest/api.rb:1
- Orphaned file lib/twilio-ruby/jwt/task_router.rb:1
- Orphaned file lib/twilio-ruby/jwt/access_token.rb:1
- Orphaned file lib/twilio-ruby/rest/preview.rb:1
- Orphaned file lib/twilio-ruby/twiml/twiml.rb:1
- Orphaned file lib/twilio-ruby/rest/supersim.rb:1
- Orphaned file lib/twilio-ruby/rest/trusthub.rb:1
- Orphaned file lib/twilio-ruby/rest/conversations.rb:1
- Orphaned file lib/twilio-ruby/twiml/messaging_response.rb:1
- Orphaned file lib/twilio-ruby/jwt/client_capability.rb:1
- Orphaned file lib/twilio-ruby/framework/rest/page.rb:1
- Duplicated predicate lib/twilio-ruby/framework/rest/page.rb:54
- Duplicated predicate lib/twilio-ruby/framework/rest/page.rb:42
- Duplicated predicate lib/twilio-ruby/base/client_base.rb:108
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:3
- Ruby's type checker does not check nil everywhere
Minor — 4 finding(s)
- Outdated: faraday
- Outdated: jwt
- Outdated: nokogiri
- Outdated: simplecov
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b7b92282e08f4251b31faa357153c44e/history.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b7b92282e08f4251b31faa357153c44e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude lib/twilio-ruby/rest/accounts --exclude lib/twilio-ruby/rest/api --exclude lib/twilio-ruby/rest/bulkexports --exclude lib/twilio-ruby/rest/chat --exclude lib/twilio-ruby/rest/content --exclude lib/twilio-ruby/rest/conversations --exclude lib/twilio-ruby/rest/events --exclude lib/twilio-ruby/rest/flex_api --exclude lib/twilio-ruby/rest/frontline_api --exclude lib/twilio-ruby/rest/iam --exclude lib/twilio-ruby/rest/insights --exclude lib/twilio-ruby/rest/intelligence --exclude lib/twilio-ruby/rest/ip_messaging --exclude lib/twilio-ruby/rest/knowledge --exclude lib/twilio-ruby/rest/lookups --exclude lib/twilio-ruby/rest/marketplace --exclude lib/twilio-ruby/rest/memory --exclude lib/twilio-ruby/rest/messaging --exclude lib/twilio-ruby/rest/monitor --exclude lib/twilio-ruby/rest/notify --exclude lib/twilio-ruby/rest/numbers --exclude lib/twilio-ruby/rest/oauth --exclude lib/twilio-ruby/rest/preview --exclude lib/twilio-ruby/rest/preview_iam --exclude lib/twilio-ruby/rest/pricing --exclude lib/twilio-ruby/rest/proxy --exclude lib/twilio-ruby/rest/routes --exclude lib/twilio-ruby/rest/serverless --exclude lib/twilio-ruby/rest/studio --exclude lib/twilio-ruby/rest/supersim --exclude lib/twilio-ruby/rest/sync --exclude lib/twilio-ruby/rest/taskrouter --exclude lib/twilio-ruby/rest/trunking --exclude lib/twilio-ruby/rest/trusthub --exclude lib/twilio-ruby/rest/verify --exclude lib/twilio-ruby/rest/video --exclude lib/twilio-ruby/rest/voice --exclude lib/twilio-ruby/rest/webhooks --exclude lib/twilio-ruby/rest/wireless . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |