@almadar/core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/schema-DgAnrD1M.d.ts | AI (source-diff): TypeScript declaration file with readable JSDoc and type definitions; long lines are bundled Zod schema types, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-C61Wxi3a.d.ts | AI (source-diff): TypeScript declaration file with readable JSDoc and type definitions; long lines are bundled Zod schema types, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-Qc9OOui3.d.ts | AI (source-diff): Large bundled .d.ts file from tsup; sample shows readable type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-S6adsRKG.d.ts | AI (source-diff): Generated TypeScript declaration file with long Zod schema type signatures; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/schema-ChiLwvNY.d.ts | AI (source-diff): Generated TypeScript declaration file with long Zod schema type signatures; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/schema-TBowD2oF.d.ts | AI (source-diff): Bundled .d.ts rollup from tsup; long lines are concatenated type declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-CvzQvW-e.d.ts | AI (source-diff): Same pattern: tsup-generated declaration bundle with readable JSDoc and type definitions. | ai | |
| source-diff | obfuscated-file:dist/trait-FCfo_4jF.d.ts | AI (source-diff): TypeScript declaration file with long Zod schema type signatures; readable JSDoc and type definitions confirm no obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-BEBX7aQ3.d.ts | AI (source-diff): TypeScript declaration file with long Zod schema type signatures; readable JSDoc and type definitions confirm no obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-BdATnYqq.d.ts | AI (source-diff): Bundled TypeScript declaration file from tsup; long lines are rolled-up type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-DmoY7UHh.d.ts | AI (source-diff): Bundled TypeScript declaration file from tsup; long lines are rolled-up type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-g5-2JR48.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled Zod schema types; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/schema-Cov1FvVJ.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled Zod schema types; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/schema-CgNnvuCR.d.ts | AI (source-diff): Large bundled .d.ts file from tsup; long lines are concatenated type declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-DRDVNvPf.d.ts | AI (source-diff): Large .d.ts files with long lines are normal tsup-bundled type declarations; sample shows readable TypeScript, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-Dx404jRG.d.ts | AI (source-diff): Bundled TypeScript declaration file from tsup; long lines are rolled-up type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-BjSJtFXv.d.ts | AI (source-diff): Same pattern: bundled .d.ts output with readable JSDoc and type definitions; stable for this build toolchain. | ai | |
| source-diff | obfuscated-file:dist/schema-B9mHgRPp.d.ts | AI (source-diff): Long lines in .d.ts files are from bundled Zod schema type inference, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/trait-Bs8Bo9_z.d.ts | AI (source-diff): Bundled .d.ts type rollup from tsup; long lines are inlined TypeScript types, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-zAvm81vl.d.ts | AI (source-diff): Bundled .d.ts type rollup from tsup; long lines are inlined TypeScript types, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-Bryabp9C.d.ts | AI (source-diff): Generated .d.ts bundle from tsup; long lines are type declarations, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/schema-B-92HhgX.d.ts | AI (source-diff): Large bundled .d.ts file from tsup; sample shows readable TypeScript type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-pKqQXuGN.d.ts | AI (source-diff): tsup-bundled .d.ts with long Zod type signatures; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-D1kGh81D.d.ts | AI (source-diff): Bundled .d.ts type declaration file; long lines are normal for tsup-generated trait type exports. | ai | |
| source-diff | obfuscated-file:dist/schema--EDm7mx5.d.ts | AI (source-diff): Bundled .d.ts type declaration file; long lines are normal for tsup-generated schema type exports. | ai | |
| source-diff | obfuscated-file:dist/trait-BV1DyJ2A.d.ts | AI (source-diff): Bundled .d.ts type declaration file from tsup; long lines are rolled-up type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-Dp98Xt5i.d.ts | AI (source-diff): Bundled .d.ts type declaration file from tsup; long lines are rolled-up type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-CSAEAlE6.d.ts | AI (source-diff): Large .d.ts file with long lines is bundled TypeScript declarations from tsup; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-Bzv2COpe.d.ts | AI (source-diff): Same pattern: bundled TypeScript declaration file with readable types and JSDoc, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/schema-B5-kHxVf.d.ts | AI (source-diff): Long lines are Zod schema type signatures in a bundled .d.ts file — standard tsup output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-DEkM0GfA.d.ts | AI (source-diff): File is a tsup-generated bundled .d.ts declaration file with readable type definitions; long lines are normal for declaration rollups. | ai | |
| source-diff | obfuscated-file:dist/schema-WX5fN1Ra.d.ts | AI (source-diff): Large bundled .d.ts type rollup from tsup; long lines are expected, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-C23jbaBB.d.ts | AI (source-diff): Bundled TypeScript declaration file from tsup; long lines are type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-Dp3KfQHm.d.ts | AI (source-diff): Bundled TypeScript declaration file from tsup; long lines are type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-BPe356_9.d.ts | AI (source-diff): Same pattern: bundled TypeScript declarations with long Zod schema types, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/schema-Bg4qX43l.d.ts | AI (source-diff): Long lines in .d.ts are bundled Zod type signatures from tsup; readable JSDoc comments confirm no obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-Dh8USts-.d.ts | AI (source-diff): Same pattern: readable TypeScript declarations with long Zod type lines from bundler output. | ai | |
| source-diff | obfuscated-file:dist/schema-oigeZDco.d.ts | AI (source-diff): Long lines are Zod schema type signatures in .d.ts files — standard tsup output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-DyPfxNwk.d.ts | AI (source-diff): Generated .d.ts bundle from tsup; long lines are type unions, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/schema-mcIpWPzS.d.ts | AI (source-diff): Long lines in .d.ts files are Zod schema type signatures from tsup bundling, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-BVLBQ9uk.d.ts | AI (source-diff): Long lines in .d.ts files are Zod schema type signatures from tsup bundling, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-DJzXvJHi.d.ts | AI (source-diff): Large bundled .d.ts declaration file from tsup; long lines are type definitions, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/schema-BQCTssuv.d.ts | AI (source-diff): Bundled .d.ts type declaration file from tsup; long lines are concatenated type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-Cvs0OQbV.d.ts | AI (source-diff): Bundled .d.ts type declaration file from tsup; long lines are concatenated type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/trait-DvvM-71c.d.ts | AI (source-diff): Same pattern: bundled .d.ts with readable interfaces and Zod schemas; long lines are a tsup artifact, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-B6gRJD4J.d.ts | AI (source-diff): TypeScript declaration file with readable JSDoc and type defs; long lines are bundled Zod schema types from tsup, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-BVni4uNf.d.ts | AI (source-diff): Large .d.ts bundle from tsup; long lines are concatenated type declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-BAT_cYlE.d.ts | AI (source-diff): Large bundled .d.ts file from tsup; sample shows readable TypeScript type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-BQhPDGd_.d.ts | AI (source-diff): Large .d.ts file with readable JSDoc and typed interfaces; long lines are bundled type unions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-VTi4U3sS.d.ts | AI (source-diff): Large bundled .d.ts file from tsup; sample shows readable TypeScript type declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-C3iwMsTl.d.ts | AI (source-diff): Generated .d.ts bundle from tsup; long lines are normal for bundled TypeScript declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-CI7VxcmO.d.ts | AI (source-diff): Generated .d.ts bundle from tsup; long lines are type definitions, not obfuscated code. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/schema-Bvgo3r3r.d.ts | AI (source-diff): File is a bundled .d.ts type declaration; long lines are from concatenated type defs, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-OhIbVaYu.d.ts | AI (source-diff): File is a bundled .d.ts with long type union lines, not obfuscated code; pattern is expected for tsup-built declaration bundles. | ai | |
| source-diff | obfuscated-file:dist/schema-CLFPg1xW.d.ts | AI (source-diff): Large generated .d.ts from tsup/zod schema; long lines are normal for bundled type declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-rdjNjALB.d.ts | AI (source-diff): Generated .d.ts schema bundle from tsup; long lines are normal for large zod schema type declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-BFnZrBhm.d.ts | AI (source-diff): Large .d.ts files with long lines are normal tsup/zod output; sample confirms legitimate type declarations. | ai | |
| source-diff | obfuscated-file:dist/schema-D3qNm2Ac.d.ts | AI (source-diff): Large generated .d.ts from tsup build; long lines are type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-4TWKcBt4.d.ts | AI (source-diff): Large .d.ts file is a bundled zod schema type declaration; long lines are expected from tsup-generated type rollups, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-DI8_HaRx.d.ts | AI (source-diff): Large bundled .d.ts file from tsup build; long lines are normal for generated TypeScript declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-BY-2YP2q.d.ts | AI (source-diff): Large bundled .d.ts with long lines from tsup; sample shows readable JSDoc/type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-Dy3r-r80.d.ts | AI (source-diff): Large generated .d.ts from tsup/zod schema; long lines are normal for bundled type declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-aGK1-NnG.d.ts | AI (source-diff): Large bundled .d.ts from tsup/zod schema; long lines are normal for generated TypeScript declaration files, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-B2HUtPrQ.d.ts | AI (source-diff): Large .d.ts declaration file generated by bundler; long lines are normal for bundled type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-Cm63mgSP.d.ts | AI (source-diff): Large .d.ts file is a bundler-generated TypeScript declaration file (tsup with content-hash suffix). Long lines are typical of inlined type declarations, not obfuscation. Content sample confirms legitimate schema type definitions. | ai | |
| source-diff | obfuscated-file:dist/schema-obC5T1Jm.d.ts | AI (source-diff): This is a bundled TypeScript declaration file (.d.ts) generated by tsup. Long lines are a known artifact of bundled type declarations, not obfuscation. Content is clearly readable type definitions. | ai | |
| source-diff | obfuscated-file:dist/schema-DmrHbrqM.d.ts | AI (source-diff): This is a bundled TypeScript declaration file (.d.ts) generated by tsup with content-hash naming. Long lines are from concatenated type definitions, not obfuscation. No runtime execution risk. | ai | |
| source-diff | obfuscated-file:dist/schema-DFOz4rEu.d.ts | AI (source-diff): This is a tsup-bundled TypeScript declaration file. Long lines are from auto-generated type definitions, not obfuscation. Sample confirms readable, legitimate schema types. | ai | |
| source-diff | obfuscated-file:dist/schema-N46ASk3M.d.ts | AI (source-diff): The flagged file is a large auto-generated TypeScript declaration bundle (.d.ts). It contains only type definitions, no executable code. Long lines are from generated type unions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/schema-DYj-zJWb.d.ts | AI (source-diff): File is a generated TypeScript declaration (.d.ts) with verbose Zod schema types. Long lines are from generated type definitions, not obfuscation. Consistent with tsup build output for this package. | ai | |
| provenance | missing-githead | AI (provenance): Publisher has 23 approved packages with 0 rejections; missing gitHead reflects a CI environment change, not a malicious publish. Repository URL is present and consistent. | ai | |
| source-diff | obfuscated-file:dist/schema-zGCZtr5W.d.ts | AI (source-diff): File is a tsup-generated TypeScript declaration file with long type union lines, not obfuscation. Hash in filename is standard bundler content-addressing. Sample confirms readable, documented type definitions. | ai | |
| source-diff | obfuscated-file:dist/schema-DKSddYoB.d.ts | AI (source-diff): File is a tsup-generated TypeScript declaration bundle with content-hash suffix. Long lines are from inlined type declarations, not obfuscation. Sample shows legitimate schema type definitions. | ai | |
| source-diff | obfuscated-file:dist/schema-BrFR8WMF.d.ts | AI (source-diff): Large .d.ts file generated by tsup bundler with content-hash suffix; long lines are bundled TypeScript type declarations, not obfuscated executable code. Stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/schema-DnLtWO4e.d.ts | AI (source-diff): File is an auto-generated TypeScript declaration (.d.ts) bundle from tsup. Long lines are a build artifact, not obfuscation. No runtime execution risk from .d.ts files. | ai | |
| source-diff | obfuscated-file:dist/schema-BmRZkOwH.d.ts | AI (source-diff): File is a bundled TypeScript declaration (.d.ts) generated by tsup; long lines are auto-generated type definitions, not obfuscated code. Pattern is stable for this package's build output. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @almadar/core is a scoped package named 'core' as in the core library of the Almadar project, not an impersonation of the 'cors' package. The Levenshtein match is coincidental. | ai |
Versions (showing 51 of 140)
| Version | Deps | Published |
|---|---|---|
| 9.9.0 | 2 / 7 | |
| 9.8.0 | 2 / 7 | |
| 9.7.0 | 2 / 7 | |
| 9.6.1 | 2 / 7 | |
| 9.6.0 | 2 / 7 | |
| 9.5.0 | 2 / 7 | |
| 9.4.0 | 2 / 7 | |
| 9.3.0 | 2 / 7 | |
| 9.2.0 | 2 / 7 | |
| 9.1.1 | 2 / 7 | |
| 9.1.0 | 2 / 7 | |
| 9.0.1 | 2 / 7 | |
| 9.0.0 | 2 / 7 | |
| 8.8.2 | 2 / 7 | |
| 8.8.1 | 2 / 7 | |
| 8.8.0 | 2 / 7 | |
| 8.7.4 | 2 / 7 | |
| 8.7.3 | 2 / 7 | |
| 8.7.2 | 2 / 7 | |
| 8.7.0 | 2 / 7 | |
| 8.6.3 | 2 / 7 | |
| 8.6.2 | 2 / 7 | |
| 8.6.1 | 2 / 7 | |
| 8.6.0 | 2 / 7 | |
| 8.5.1 | 2 / 7 | |
| 8.5.0 | 2 / 7 | |
| 8.4.0 | 2 / 7 | |
| 8.3.0 | 2 / 7 | |
| 8.2.0 | 2 / 7 | |
| 8.1.0 | 2 / 7 | |
| 8.0.0 | 2 / 7 | |
| 7.26.0 | 2 / 7 | |
| 7.25.0 | 2 / 7 | |
| 7.24.0 | 2 / 7 | |
| 7.23.0 | 2 / 7 | |
| 7.22.0 | 2 / 7 | |
| 7.21.0 | 2 / 7 | |
| 7.20.0 | 2 / 7 | |
| 7.19.1 | 2 / 7 | |
| 7.19.0 | 2 / 7 | |
| 7.18.0 | 2 / 7 | |
| 7.17.0 | 2 / 7 | |
| 7.16.0 | 2 / 7 | |
| 7.15.1 | 2 / 7 | |
| 7.14.3 | 2 / 7 | |
| 7.14.2 | 2 / 7 | |
| 7.14.1 | 2 / 7 | |
| 7.14.0 | 2 / 7 | |
| 7.13.0 | 2 / 7 | |
| 7.12.0 | 2 / 7 | |
| 7.11.0 | 2 / 7 |
v9.9.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.