Was das Netzwerk gefunden hat
Jede Zeile hier ist eine Messung, keine Meinung. Jede verweist auf ein veröffentlichtes Sample, dessen Contract in einem gepinnten Container ohne Netzzugang ausgeführt wird — Sie können ihn erneut ausführen und dem Ergebnis widersprechen.
Betriebssystem und Runtime stammen aus der aufgezeichneten Sample-Umgebung; fehlende Dimensionen werden ausgeschlossen.
597 Befunde aus 8 Ökosystemen.
- cargo
- composer
- gem
- golang
- hex
- npm
- pub
- pypi
Vom Sample behauptet, vom Vertrag gemessen
376–400 von 568, gemessen von veröffentlichten Samples.
-
npmSample-Vertragnode · linux/x64core-js@3.49.0
AngenommenA naive expectation is that `Iterator.range` coerces `NaN` arguments to usable numbers, so `Iterator.range(NaN, 10)` would still return an iterable.
GemessenCalling `Iterator.range` with `NaN` as `start` throws `RangeError` in the patched `core-js` behavior.
-
npmSample-Vertragnode · linux/x64commander@15.0.0
AngenommenAn 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.
GemessenPassing -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.
-
npmSample-Vertragnode · linux/x64commander@13.1.0
AngenommenParsing multiple command invocations concurrently with parseAsync on a shared Command instance keeps options isolated within each execution promise.
GemessenCalling 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.
-
npmSample-Vertragnode · linux/x64commander@15.0.0
AngenommenAn 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.
GemessenOption.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.
-
npmSample-Vertragnode · linux/x64bun@1.3.14
AngenommenPinning bun in package.json should let Node import it as a normal dependency module.
Gemessenbun@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.
-
npmSample-Vertragnode · linux/x64bun@1.3.14
AngenommenBun 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.
GemessenBun.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
-
npmSample-Vertragnode · linux/x64@babel/preset-env@7.26.9
AngenommenTargeting 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.
GemessenEven 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.
-
npmSample-Vertragnode · linux/x64@babel/preset-env@8.0.2
AngenommenTargeting 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.
GemessenWhen 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.
-
npmSample-Vertragnode · linux/x64@babel/core@8.0.1
AngenommenEquivalent inline plugin option objects are reused across transformSync calls, and createConfigItem remains a synchronous convenience API in Babel 8.
GemessenA ConfigItem created once with createConfigItemSync reuses its plugin descriptor so five transformSync calls execute the factory exactly once
-
npmSample-Vertragnode · linux/x64@babel/core@8.0.1
AngenommenCalling 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.
Gemessenbabel.transformAsync completes AST traversal synchronously and generates untransformed output code when a plugin visitor returns a Promise, leaving the Promise un-awaited.
-
npmSample-Vertragnode · linux/x64@babel/core@8.0.1
AngenommentransformFromAstSync modifies the provided AST object in place during traversal and populates result.ast with the transformed tree.
GemessentransformFromAstSync preserves the input AST node unmodified and sets result.ast to null unless cloneInputAst is set to false and ast is set to true.
-
npmSample-Vertragnode · linux/x64@babel/core@8.0.1
Angenommenbabel.transformSync automatically discovers and loads .babelrc configuration files from the current working directory when transforming code strings.
Gemessenbabel.transformSync and babel.loadPartialConfigSync ignore .babelrc configuration files when filename is omitted, defaulting options.babelrc to false
-
npmSample-Vertragnode · linux/x64@babel/core@8.0.1
AngenommenSetting configFile: false disables all filesystem configuration loading, while subpackage .babelrc.json configurations are discovered and applied automatically.
GemessenSetting 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
-
hexSample-Vertragelixir · linux/x64nimble_pool@1.1.0
AngenommenNimblePool.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.
GemessenReturning {: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.
-
golangSample-Vertraggo · linux/x64net/http@go1.26.5
AngenommenHeaders set on http.ResponseWriter after calling WriteHeader are included in the HTTP response.
GemessenHeaders set on http.ResponseWriter after calling WriteHeader are omitted from the client response.
-
golangSample-Vertraggo · linux/x64net/http@v1.26.5
AngenommenSetting the Host header via http.Request.Header.Set("Host", ...) overrides the Host header sent on the wire by http.Client.
Gemessenreq.Header.Set("Host", ...) does not override the wire Host header sent by http.Client
-
golangSample-Vertraggo 1.26 · linux/x64gorm.io/gorm@v1.31.2
AngenommenCalling Scopes(Tenant(id)) before Where(...).Or(...) keeps the tenant predicate in force for both OR branches because the scope appears first in the chain.
Gemessenassert 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
-
golangSample-Vertraggo 1.26 · linux/x64google.golang.org/grpc@v1.83.0
AngenommenA unary client interceptor can call metadata.NewOutgoingContext to add its own field without affecting outgoing metadata the caller already attached.
GemessenA grpc.NewClient call reaches a manually registered unary service through bufconn, a context dialer, and insecure transport credentials without opening a TCP listener.
-
golangSample-Vertraggo 1.26 · linux/x64github.com/spf13/viper@v1.21.0
AngenommenMergeConfigMap 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.
Gemessenassert MergeConfigMap lowercases both top-level and nested keys in the caller-supplied maps themselves
-
golangSample-Vertraggo · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
Angenommenproviding 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
Gemessenassert jwt.Parse returns jwt.ErrTokenSignatureInvalid when a key of invalid type is provided for RSA verification, rather than ErrTokenUnverifiable or ErrInvalidKeyType directly
-
golangSample-Vertraggo · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
AngenommenDefining 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.
GemessenDefining 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.
-
golangSample-Vertraggo · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
AngenommenA single-element jwt.ClaimStrings slice serializes to a JSON string value by default.
GemessenSerializing a single-element jwt.ClaimStrings audience produces a JSON array by default because jwt.MarshalSingleStringAsArray is true.
-
golangSample-Vertraggo · linux/x64github.com/golang-jwt/jwt/v5@v5.2.2
AngenommenParseUnverified returns a slice containing all split string segments when parsing a malformed token string with extra dot delimiters.
GemessenParseUnverified returns a nil parts slice rather than a populated slice of all split segments when given a token with extra dot delimiters.
-
golangSample-Vertraggo · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
AngenommenDefining a Valid() error method on a custom claims struct validates claims during jwt.ParseWithClaims.
Gemessenjwt.ParseWithClaims silently ignores a custom claims Valid() error method, passing validation unless the struct implements ClaimsValidator with Validate() error.
-
golangSample-Vertraggo · linux/x64github.com/go-chi/chi/v5@v5.2.1
Angenommenmiddleware.AllowContentType rejects POST requests lacking a Content-Type header and ignores Content-Type headers on GET requests.
Gemessenmiddleware.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
Wie Sie jede Zeile hier prüfen
Öffnen Sie das Sample, lesen Sie seinen Contract, führen Sie ihn aus. Der Contract ist der eigene Test des Samples: Er läuft ohne Netz in einem gepinnten Container, und die signierte Quittung dieses Laufs ist das, was das Netzwerk speichert. Nichts hier hängt davon ab, wie wir eine Bibliothek lesen — nur davon, was sie getan hat.
Einige veröffentlichte Beispiele stehen nicht auf dieser Seite. Ihr Vertrag ist bestanden und das Beispiel ist live — aber keine Zeile dieses Vertrags liest sich als Satz. Eine Zusicherung wie expect(x).toBe(1) sagt neben der Annahme, die sie prüft, niemandem etwas. Sie bleiben lieber draußen, als als Beleg zu erscheinen, den niemand lesen kann.