@nexeraid/identity-schemas
This is where we store Zod Schemas for our code base.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/vault.schema-229df6cc.cjs.prod.cjs | AI (source-diff): Standard minified CJS prod bundle; visible code is Babel-transpiled schema logic, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/vault.schema-ed6f19b1.cjs.dev.cjs | AI (source-diff): Standard minified CJS dev bundle; same pattern as prod bundle, normal build artifact. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package (@nexeraid) with 401 versions and inbound approved edges; sparse metadata is a style choice, not spam. | ai | |
| phantom-deps | phantom-dep:remeda | AI (phantom-deps): Monorepo/build-tool pattern; stable false positive for this org's packages. | ai | |
| phantom-deps | phantom-dep:@nexeraid/logger | AI (phantom-deps): Same org scope; likely used transitively or in build config, not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@hono/zod-openapi | AI (phantom-deps): Referenced in config files only; stable false positive for this package's build setup. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.222.0 | 7 / 10 | |
| 2.220.0 | 7 / 10 | |
| 2.219.0 | 7 / 10 | |
| 2.218.0 | 7 / 10 |
v2.222.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.
v2.220.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.219.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.218.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.