Skip to main content

Programming Languages

Language specifications and standards

28
Standards
20
Products

Standards

ISO/IEC 14882:2023 (C++23)

Adhering to ISO/IEC standards during software migrations is crucial for ensuring quality, mitigating risks, and maintaining compliance. This comprehensive guide outlines the purpose of these standards, key compliance considerations, and actionable steps to facilitate successful migrations while addressing common challenges faced by teams.

by ISO/IEC Joint Technical Committee

cpp-23

ISO/IEC 14882:2020 (C++20)

Unlock seamless data and code migration with ISO/IEC 14882:2020 (C++20). Explore migration standards for optimal cloud transformation today!

by ISO/IEC Joint Technical Committee

cpp-20

ISO/IEC 14882:2017 (C++17)

Adhering to ISO/IEC standards during software migrations is essential for ensuring quality, compliance, and stakeholder confidence. This comprehensive guide provides practical insights on key requirements, implementation strategies, and tools to facilitate successful migrations while addressing common challenges organizations may face.

by ISO/IEC Joint Technical Committee

cpp-17

ISO/IEC 14882:2014 (C++14)

Adhering to ISO/IEC standards is vital for successful software migrations, ensuring quality, security, and compliance. This guide provides practical insights on how to implement these standards effectively, addressing key requirements, tools, and common challenges faced by teams during the migration process.

by ISO/IEC Joint Technical Committee

cpp-14

ISO/IEC 9899:2018 (C18)

Adhering to ISO/IEC standards during software migrations is crucial for minimizing risks, ensuring data integrity, and meeting compliance obligations. This guide outlines key requirements, practical steps for adherence, and tools that help maintain compliance, empowering teams to navigate their migration projects confidently and efficiently.

by ISO/IEC Joint Technical Committee

c18

ISO/IEC 9899:2011 (C11)

ISO/IEC standards play a crucial role in ensuring quality and compliance during software migrations. By understanding these standards and implementing best practices, teams can mitigate risks, enhance stakeholder confidence, and navigate the complexities of migration projects effectively.

by ISO/IEC Joint Technical Committee

c11

ECMA-262 2024 (ES2024)

Understanding and adhering to ECMA standards is essential for successful software migrations, ensuring interoperability, risk mitigation, and regulatory compliance. By following best practices, utilizing the right tools, and addressing common challenges, teams can navigate the complexities of migration projects with confidence and clarity.

by Ecma International

javascript-es2024

ECMA-262 2015 (ES6)

Adhering to ECMA standards during software migrations is crucial for ensuring interoperability, data integrity, and future-proofing systems. By understanding key requirements, utilizing appropriate tools, and addressing common challenges, teams can facilitate smoother transitions from legacy systems to modern platforms, ultimately reducing risks and enhancing collaboration.

by Ecma International

javascript-es6

ISO/IEC 30170:2022 (Ruby 3.1)

Adhering to ISO/IEC standards during software migrations is essential for ensuring quality, security, and compliance. This guide outlines the importance of these standards, key requirements for migration projects, and practical strategies for maintaining compliance, helping teams navigate their transitions with confidence and efficiency.

by ISO/IEC Joint Technical Committee

ruby-3-1

ECMA-334 6th (C# 11)

Understanding the ECMAScript standard is critical for teams planning software migrations, as it ensures compatibility, reduces risks, and promotes efficient development practices. By following compliance guidelines and leveraging the right tools, teams can navigate the complexities of migration while maintaining code quality and performance.

by Ecma International

csharp-11

Java SE 17 (JSR 392)

Adhering to technical standards during software migrations is essential for ensuring data integrity, security, and stakeholder confidence. This comprehensive guide outlines the purpose of these standards, key compliance considerations, and practical steps to maintain adherence throughout the migration process, ultimately facilitating a smoother transition to modern platforms.

by Oracle

java-se-17

Java SE 8 (JSR 337)

Adhering to Oracle migration standards is crucial for ensuring data integrity, system compatibility, and regulatory compliance during software migrations. By implementing a structured approach and utilizing the right tools, teams can navigate common challenges and achieve successful transitions to modern Oracle solutions.

by Oracle

java-se-8

Python 3.12 (PEP 693)

Understanding and adhering to Python standards during software migrations is crucial for ensuring code clarity, compatibility, and maintainability. By following key guidelines such as PEP 8 compliance, implementing comprehensive testing, and utilizing effective tools, teams can mitigate risks and foster collaboration, ultimately ensuring a successful migration process.

by Python Software Foundation

python-3-12

Python PEP 8 (Style Guide)

Understanding migration standards in Python is crucial for ensuring seamless transitions from legacy systems. By adhering to these standards, teams can mitigate risks, maintain security, and enhance performance during migrations. Practical steps and tools can further support compliance, leading to successful project outcomes.

by Python Software Foundation

pep-8

Go 1.22 Spec

Compliance standards are essential for successful software migrations, helping organizations protect sensitive data, maintain system integrity, and adhere to legal requirements. By following best practices and using appropriate tools, teams can ensure their migration projects meet compliance standards, mitigating risks and fostering stakeholder trust.

by Google

go-1-22

Rust 1.78 Edition 2024

Migrating systems that utilize Rust requires adherence to its safety and performance standards. By leveraging Rust's ownership model, error handling capabilities, and robust tooling, teams can ensure a successful transition while mitigating common challenges. Following these guidelines will lead to safer, more reliable applications post-migration.

by Rust Foundation

rust-2024

Swift 5.9 Language Guide

Understanding Apple's migration standards is crucial for teams planning software migrations. These standards ensure data integrity, user privacy, and security, helping organizations execute migrations effectively while minimizing risks. By following key requirements and leveraging the right tools, teams can maintain compliance and address common challenges throughout the migration process.

by Apple

swift-5-9

Kotlin 2.0 Spec

Understanding and adhering to established migration standards is crucial for successful software transitions. These standards help mitigate risks, ensure data integrity, and maintain compliance, leading to a smoother migration process. By leveraging the right tools and processes, teams can address common challenges and execute migrations with confidence.

by JetBrains

kotlin-2-0

PHP 8.3 Spec

Adhering to PHP standards during software migrations is vital for ensuring code quality, consistency, and maintainability. By following established guidelines, utilizing appropriate tools, and addressing challenges proactively, teams can achieve successful migrations that integrate legacy systems into modern frameworks effectively.

by PHP Foundation

php-8-3

Perl 5.38 Syntax

Adhering to Perl standards during software migrations is crucial for ensuring code compatibility, maintaining best practices, and streamlining the transition process. By conducting thorough code audits, implementing robust testing protocols, and utilizing effective tools, teams can navigate the complexities of migration with confidence and achieve successful outcomes.

by Perl Foundation

perl-5-38

TypeScript 5.4 Spec

Adhering to Microsoft standards during software migrations is essential for ensuring security, performance, and regulatory compliance. By understanding these standards and implementing best practices, teams can navigate migration complexities effectively, minimizing risks and maximizing efficiency.

by Microsoft

typescript-5-4

Scala 3.4 Reference

EPFL standards are essential for ensuring quality and compliance in software migrations. By following these guidelines, teams can enhance reliability, streamline processes, and maintain compliance, significantly reducing the risks associated with transitioning from legacy systems to modern platforms.

by EPFL

scala-3-4

Erlang/OTP 26

Understanding and adhering to Ericsson's technical standards is essential for successful software migrations. These standards provide a framework for ensuring data protection, interoperability, and performance, thereby mitigating risks and enhancing efficiency. By following best practices and leveraging appropriate tools, teams can navigate the complexities of migration while maintaining compliance with industry standards.

by Ericsson

erlang-26

Elixir 1.17

Ericsson's migration standards provide a comprehensive framework for ensuring smooth and secure software transitions. By adhering to these guidelines, teams can mitigate risks, enhance efficiency, and maintain stakeholder trust throughout the migration process.

by Ericsson

elixir-1-17

Haskell 2010 Report

Understanding Haskell standards is crucial for teams migrating Haskell-based applications. By adhering to Haskell's principles of type safety, functional purity, and modularity, developers can ensure more reliable and maintainable migrations. This guide provides actionable insights and tools to navigate the complexities of Haskell migrations effectively.

by Haskell Foundation

haskell-2010

ISO/IEC 23270:2006 (C# 2.0)

Understanding ISO/IEC standards is essential for successful software migrations, as they provide a framework for quality assurance, data security, and interoperability. By adhering to these standards, organizations can mitigate risks, enhance trust, and improve operational efficiency during migration projects. This guide outlines key requirements, compliance considerations, and practical tools to ensure your migrations align with recognized standards.

by ISO/IEC Joint Technical Committee

csharp-2-0

OCaml 5.2 Spec

Understanding and adhering to technical standards during software migrations is essential for minimizing risks, enhancing efficiency, and building stakeholder confidence. By following established guidelines and employing the right tools, teams can ensure data integrity, security compliance, and successful interoperability throughout the migration process.

by INRIA

ocaml-5-2

ISO/IEC 13211-1:1995 (Prolog)

Understanding the ISO/IEC standard is essential for successful software migrations, ensuring data integrity, security, and compliance. This framework provides essential guidelines that help organizations manage risks, enhance operational efficiency, and foster stakeholder trust, making it a key component of any migration strategy.

by ISO/IEC Joint Technical Committee

prolog-1995

Products & Technologies

Java

High-level, class-based, object-oriented programming language

Python

High-level, interpreted programming language with dynamic semantics

JavaScript

High-level, dynamic programming language for web development

TypeScript

Strongly typed programming language that builds on JavaScript

Go

Statically typed, compiled programming language designed at Google

Rust

Systems programming language focused on safety, speed, and concurrency

C#

Modern, object-oriented programming language developed by Microsoft

Kotlin

Modern, concise programming language for JVM, Android, and multiplatform

Swift

Powerful and intuitive programming language for Apple platforms

Ruby

Dynamic, open source programming language with focus on simplicity

PHP

Popular general-purpose scripting language suited for web development

Scala

Functional and object-oriented programming language for JVM

Elixir

Functional programming language running on Erlang VM

Clojure

Dynamic, functional programming language for JVM

Haskell

Purely functional programming language with strong static typing

C++

General-purpose programming language with object-oriented features

C

General-purpose programming language for system programming

Dart

Client-optimized language for fast apps on any platform

R

Programming language for statistical computing and graphics

Julia

High-level, high-performance programming language for technical computing

08:53Z[DRIFT]Next.jsNext.js is 2 major versions behind (current: 14.2.35, latest: 16.1.6).
08:54Z[OWASP]A03:2021 – InjectionUnescaped user input rendered into HTML template (src/routes/admin.ts:42)
08:52Z[SCANNER]semgrepscan signature set is up to date
08:48Z[DRIFT]of dependencies are 2+ major versions behind in acme.39% of dependencies are 2+ major versions behind in acme.
08:50Z[OWASP]A02:2021 – Cryptographic FailuresJWT secret is hardcoded — use environment variables (src/auth/jwt.ts:18)
08:45Z[SCANNER]gitleaksscan signature set is up to date
08:43Z[DRIFT]@types/node@types/node is 3 major versions behind (spec: 22.15.29, latest: 25.2.3).
08:46Z[OWASP]A03:2021 – InjectionRegular expression built from user input — potential ReDoS (src/utils/search.ts:67)
08:38Z[SCANNER]trufflehogstatus: unavailable
08:38Z[DRIFT]electronelectron is 3 major versions behind (spec: ^37.6.0, latest: 40.4.1).
08:42Z[OWASP]A03:2021 – InjectiondangerouslySetInnerHTML used with potentially untrusted content (src/components/RichText.tsx:31)
08:33Z[DRIFT]@types/node@types/node is 5 major versions behind (spec: ^20.17.52, latest: 25.2.3).
08:38Z[OWASP]A05:2021 – Security MisconfigurationCookie set without httpOnly or secure flags (src/middleware/session.ts:12)
08:28Z[DRIFT]@types/supertest@types/supertest is 4 major versions behind (spec: ^2.0.16, latest: 6.0.3).
08:34Z[OWASP]A03:2021 – Injectioneval() called with dynamic expression (src/utils/template-engine.ts:88)
08:23Z[DRIFT]VitestVitest is 4 major versions behind (current: 0.34.6, latest: 4.0.18).
08:30Z[OWASP]A01:2021 – Broken Access ControlRedirect URL comes from user-controlled parameter (src/pages/auth/callback.tsx:15)
08:18Z[DRIFT]@types/node@types/node is 5 major versions behind (spec: ^20.8.0, latest: 25.2.3).
08:26Z[OWASP]A03:2021 – InjectionUnsanitised input passed to MongoDB query (src/services/users.ts:34)
08:13Z[DRIFT]vitestvitest is 4 major versions behind (spec: ^0.34.6, latest: 4.0.18).
08:22Z[OWASP]A03:2021 – InjectionChild process spawned with user-controlled arguments (src/utils/pdf-generator.ts:52)
08:08Z[DRIFT]of dependencies are 2+ major versions behind in @acme/api.31% of dependencies are 2+ major versions behind in @acme/api.
08:18Z[OWASP]A05:2021 – Security MisconfigurationExternal link opened without rel="noreferrer" (src/components/ExternalLink.tsx:8)
08:03Z[DRIFT]@types/node@types/node is 5 major versions behind (spec: ^20.11.0, latest: 25.2.3).
08:14Z[OWASP]A02:2021 – Cryptographic FailuresMath.random() used for token generation — use crypto.randomBytes (src/utils/token.ts:6)
07:58Z[DRIFT]of dependencies are 2+ major versions behind in @acme/workflow-engine.52% of dependencies are 2+ major versions behind in @acme/workflow-engine.
08:10Z[OWASP]A05:2021 – Security MisconfigurationExpress app without Helmet security headers middleware (src/server.ts:1)
07:53Z[DRIFT]@types/node@types/node is 5 major versions behind (spec: ^20.19.9, latest: 25.2.3).
07:48Z[DRIFT]@types/node@types/node is 3 major versions behind (spec: ^22.15.29, latest: 25.2.3).
08:53Z[DRIFT]Next.jsNext.js is 2 major versions behind (current: 14.2.35, latest: 16.1.6).
08:54Z[OWASP]A03:2021 – InjectionUnescaped user input rendered into HTML template (src/routes/admin.ts:42)
08:52Z[SCANNER]semgrepscan signature set is up to date
08:48Z[DRIFT]of dependencies are 2+ major versions behind in acme.39% of dependencies are 2+ major versions behind in acme.
08:50Z[OWASP]A02:2021 – Cryptographic FailuresJWT secret is hardcoded — use environment variables (src/auth/jwt.ts:18)
08:45Z[SCANNER]gitleaksscan signature set is up to date
08:43Z[DRIFT]@types/node@types/node is 3 major versions behind (spec: 22.15.29, latest: 25.2.3).
08:46Z[OWASP]A03:2021 – InjectionRegular expression built from user input — potential ReDoS (src/utils/search.ts:67)
08:38Z[SCANNER]trufflehogstatus: unavailable
08:38Z[DRIFT]electronelectron is 3 major versions behind (spec: ^37.6.0, latest: 40.4.1).
08:42Z[OWASP]A03:2021 – InjectiondangerouslySetInnerHTML used with potentially untrusted content (src/components/RichText.tsx:31)
08:33Z[DRIFT]@types/node@types/node is 5 major versions behind (spec: ^20.17.52, latest: 25.2.3).
08:38Z[OWASP]A05:2021 – Security MisconfigurationCookie set without httpOnly or secure flags (src/middleware/session.ts:12)
08:28Z[DRIFT]@types/supertest@types/supertest is 4 major versions behind (spec: ^2.0.16, latest: 6.0.3).
08:34Z[OWASP]A03:2021 – Injectioneval() called with dynamic expression (src/utils/template-engine.ts:88)
08:23Z[DRIFT]VitestVitest is 4 major versions behind (current: 0.34.6, latest: 4.0.18).
08:30Z[OWASP]A01:2021 – Broken Access ControlRedirect URL comes from user-controlled parameter (src/pages/auth/callback.tsx:15)
08:18Z[DRIFT]@types/node@types/node is 5 major versions behind (spec: ^20.8.0, latest: 25.2.3).
08:26Z[OWASP]A03:2021 – InjectionUnsanitised input passed to MongoDB query (src/services/users.ts:34)
08:13Z[DRIFT]vitestvitest is 4 major versions behind (spec: ^0.34.6, latest: 4.0.18).
08:22Z[OWASP]A03:2021 – InjectionChild process spawned with user-controlled arguments (src/utils/pdf-generator.ts:52)
08:08Z[DRIFT]of dependencies are 2+ major versions behind in @acme/api.31% of dependencies are 2+ major versions behind in @acme/api.
08:18Z[OWASP]A05:2021 – Security MisconfigurationExternal link opened without rel="noreferrer" (src/components/ExternalLink.tsx:8)
08:03Z[DRIFT]@types/node@types/node is 5 major versions behind (spec: ^20.11.0, latest: 25.2.3).
08:14Z[OWASP]A02:2021 – Cryptographic FailuresMath.random() used for token generation — use crypto.randomBytes (src/utils/token.ts:6)
07:58Z[DRIFT]of dependencies are 2+ major versions behind in @acme/workflow-engine.52% of dependencies are 2+ major versions behind in @acme/workflow-engine.
08:10Z[OWASP]A05:2021 – Security MisconfigurationExpress app without Helmet security headers middleware (src/server.ts:1)
07:53Z[DRIFT]@types/node@types/node is 5 major versions behind (spec: ^20.19.9, latest: 25.2.3).
07:48Z[DRIFT]@types/node@types/node is 3 major versions behind (spec: ^22.15.29, latest: 25.2.3).