ネットワークが見つけたもの
以下の各行は意見ではなく測定です。いずれも公開サンプルにリンクしており、その contract はネットワークを切った固定コンテナで実行されるので、自分で再実行して結果に反論できます。
OS とランタイムはリンク先サンプルに記録された環境です。その項目がない記録は選択時に除外されます。
597 件の発見、8 個のエコシステム。
- cargo
- composer
- gem
- golang
- hex
- npm
- pub
- pypi
サンプルが述べ、その契約が測ったこと
公開サンプルが測定した結果の 376–400 件目(全 568 件)。
-
npmサンプル契約node · linux/x64core-js@3.49.0
信じられていることA naive expectation is that `Iterator.range` coerces `NaN` arguments to usable numbers, so `Iterator.range(NaN, 10)` would still return an iterable.
測定結果Calling `Iterator.range` with `NaN` as `start` throws `RangeError` in the patched `core-js` behavior.
-
npmサンプル契約node · linux/x64commander@15.0.0
信じられていることAn option configured with an optional value accepts negative numbers like -1 as its argument regardless of what other short option flags are registered on the command.
測定結果Passing -1 after an optional-argument option evaluates that option to boolean true and parses -1 as a distinct flag if any single-digit short option is defined on the command hierarchy, because Commander disables negative number heuristics whenever a digit flag exists.
-
npmサンプル契約node · linux/x64commander@13.1.0
信じられていることParsing multiple command invocations concurrently with parseAsync on a shared Command instance keeps options isolated within each execution promise.
測定結果Calling parseAsync on a shared Command instance while an earlier parseAsync execution is suspended at an await overwrites the option store, causing the earlier execution to resume with option values from the later invocation.
-
npmサンプル契約node · linux/x64commander@15.0.0
信じられていることAn option configured with an optional value and a custom argParser coerces a fallback value through argParser when the flag is invoked without an argument on the command line.
測定結果Option.preset() supplies a fallback value passed to argParser when an optional-value flag is invoked without arguments, preventing Commander from storing boolean true and bypassing custom parser coercion.
-
npmサンプル契約node · linux/x64bun@1.3.14
信じられていることPinning bun in package.json should let Node import it as a normal dependency module.
測定結果bun@1.3.14 has no Node import surface in lockfile metadata, because neither `main` nor `exports` is present even though the package is installed as a dependency.
-
npmサンプル契約node · linux/x64bun@1.3.14
信じられていることBun binary APIs receive a typed array's entire backing ArrayBuffer, so passing a subarray with a non-zero offset hashes, compresses, or writes bytes outside the view.
測定結果Bun.hash produces the same result for a non-zero-offset Uint8Array view and an independent array containing only the view bytes, and a different result for the full backing array
-
npmサンプル契約node · linux/x64@babel/preset-env@7.26.9
信じられていることTargeting modern environments like Node 22 or setting targets.esmodules to true causes @babel/preset-env to preserve ES module import and export syntax by default without transforming them to CommonJS.
測定結果Even when targeting modern environments that natively support ES modules such as Node 22 or esmodules: true, @babel/preset-env defaults modules to 'auto' and transforms import and export statements into CommonJS require and exports unless the caller declares supportsStaticESM or modules is explicitly set to false.
-
npmサンプル契約node · linux/x64@babel/preset-env@8.0.2
信じられていることTargeting modern JavaScript runtimes with @babel/preset-env and default modules: 'auto' preserves native export * as ns syntax because the targeted environments natively support ECMAScript namespace re-exports.
測定結果When modules is unset or 'auto', @babel/preset-env unconditionally injects transform-export-namespace-from and desugars export * as ns statements even when targeting modern runtimes like Chrome 120 or Node 22, unless modules is explicitly false or the caller declares supportsExportNamespaceFrom.
-
npmサンプル契約node · linux/x64@babel/core@8.0.1
信じられていることEquivalent inline plugin option objects are reused across transformSync calls, and createConfigItem remains a synchronous convenience API in Babel 8.
測定結果A ConfigItem created once with createConfigItemSync reuses its plugin descriptor so five transformSync calls execute the factory exactly once
-
npmサンプル契約node · linux/x64@babel/core@8.0.1
信じられていることCalling babel.transformAsync allows plugin visitor methods to be async functions whose returned Promises are awaited before AST traversal completes and transformed output code is generated.
測定結果babel.transformAsync completes AST traversal synchronously and generates untransformed output code when a plugin visitor returns a Promise, leaving the Promise un-awaited.
-
npmサンプル契約node · linux/x64@babel/core@8.0.1
信じられていることtransformFromAstSync modifies the provided AST object in place during traversal and populates result.ast with the transformed tree.
測定結果transformFromAstSync preserves the input AST node unmodified and sets result.ast to null unless cloneInputAst is set to false and ast is set to true.
-
npmサンプル契約node · linux/x64@babel/core@8.0.1
信じられていることbabel.transformSync automatically discovers and loads .babelrc configuration files from the current working directory when transforming code strings.
測定結果babel.transformSync and babel.loadPartialConfigSync ignore .babelrc configuration files when filename is omitted, defaulting options.babelrc to false
-
npmサンプル契約node · linux/x64@babel/core@8.0.1
信じられていることSetting configFile: false disables all filesystem configuration loading, while subpackage .babelrc.json configurations are discovered and applied automatically.
測定結果Setting configFile: false disables only project-wide babel.config.json while leaving file-relative .babelrc.json active, and subpackage .babelrc.json files are ignored under default babelrcRoots: true
-
hexサンプル契約elixir · linux/x64nimble_pool@1.1.0
信じられていることNimblePool.handle_info/2 follows the same return convention as GenServer.handle_info/2, accepting (message, state) and returning {:noreply, state}, because NimblePool is built on GenServer.
測定結果Returning {:noreply, worker_state} from handle_info/2 crashes the pool process with CaseClauseError, because NimblePool routes stray messages to each idle worker's handle_info/2, then pattern-matches the result against {:ok, _}, killing the pool and making all subsequent checkouts exit with :noproc.
-
golangサンプル契約go · linux/x64net/http@go1.26.5
信じられていることHeaders set on http.ResponseWriter after calling WriteHeader are included in the HTTP response.
測定結果Headers set on http.ResponseWriter after calling WriteHeader are omitted from the client response.
-
golangサンプル契約go · linux/x64net/http@v1.26.5
信じられていることSetting the Host header via http.Request.Header.Set("Host", ...) overrides the Host header sent on the wire by http.Client.
測定結果req.Header.Set("Host", ...) does not override the wire Host header sent by http.Client
-
golangサンプル契約go 1.26 · linux/x64gorm.io/gorm@v1.31.2
信じられていることCalling Scopes(Tenant(id)) before Where(...).Or(...) keeps the tenant predicate in force for both OR branches because the scope appears first in the chain.
測定結果assert Scopes(Tenant(7)).Where("active = ?", true).Or("role = ?", "admin") generates WHERE active = ? OR role = ? AND tenant_id = ?, so SQL precedence allows active rows from other tenants
-
golangサンプル契約go 1.26 · linux/x64google.golang.org/grpc@v1.83.0
信じられていることA unary client interceptor can call metadata.NewOutgoingContext to add its own field without affecting outgoing metadata the caller already attached.
測定結果A grpc.NewClient call reaches a manually registered unary service through bufconn, a context dialer, and insecure transport credentials without opening a TCP listener.
-
golangサンプル契約go 1.26 · linux/x64github.com/spf13/viper@v1.21.0
信じられていることMergeConfigMap treats its argument as immutable input and copies it, so changing or reusing the caller's map after the call cannot alter Viper's configuration.
測定結果assert MergeConfigMap lowercases both top-level and nested keys in the caller-supplied maps themselves
-
golangサンプル契約go · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
信じられていることproviding an invalid key type (such as a byte slice instead of an RSA public key) to jwt.Parse during RSA verification returns jwt.ErrTokenUnverifiable or jwt.ErrInvalidKeyType rather than jwt.ErrTokenSignatureInvalid
測定結果assert jwt.Parse returns jwt.ErrTokenSignatureInvalid when a key of invalid type is provided for RSA verification, rather than ErrTokenUnverifiable or ErrInvalidKeyType directly
-
golangサンプル契約go · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
信じられていることDefining a Valid() error method on a custom claims struct in github.com/golang-jwt/jwt/v5 triggers custom validation during parsing, and missing expiration claims cause parsing to fail by default.
測定結果Defining a Valid() error method on a custom claims struct has no effect in v5 because custom validation requires implementing the jwt.ClaimsValidator interface via a Validate() error method.
-
golangサンプル契約go · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
信じられていることA single-element jwt.ClaimStrings slice serializes to a JSON string value by default.
測定結果Serializing a single-element jwt.ClaimStrings audience produces a JSON array by default because jwt.MarshalSingleStringAsArray is true.
-
golangサンプル契約go · linux/x64github.com/golang-jwt/jwt/v5@v5.2.2
信じられていることParseUnverified returns a slice containing all split string segments when parsing a malformed token string with extra dot delimiters.
測定結果ParseUnverified returns a nil parts slice rather than a populated slice of all split segments when given a token with extra dot delimiters.
-
golangサンプル契約go · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
信じられていることDefining a Valid() error method on a custom claims struct validates claims during jwt.ParseWithClaims.
測定結果jwt.ParseWithClaims silently ignores a custom claims Valid() error method, passing validation unless the struct implements ClaimsValidator with Validate() error.
-
golangサンプル契約go · linux/x64github.com/go-chi/chi/v5@v5.2.1
信じられていることmiddleware.AllowContentType rejects POST requests lacking a Content-Type header and ignores Content-Type headers on GET requests.
測定結果middleware.AllowContentType allows a body-less POST request with an empty Content-Type header through to the handler with HTTP 200 rather than rejecting it based on the HTTP method
ここの行を確かめる方法
サンプルを開き、contract を読み、実行してください。contract はそのサンプル自身のテストです。ネットワークを切った固定コンテナで実行され、その実行の署名済みレシートがネットワークに保存されます。ここに書かれていることはライブラリについての解釈ではなく、ライブラリが実際に行ったことだけに基づいています。
公開済みのサンプルのうち、このページにないものがあります。契約は通過しておりサンプルも生きていますが、その契約に文として読める行がないからです。expect(x).toBe(1) のような断言は、検査している思い込みの隣に置いても読者に何も伝えません。読めない証拠を載せるより、空けておくことを選びました。