@nocobase/auth
<video width="100%" controls> <source src="https://github.com/user-attachments/assets/4d11a87b-00e2-48f3-9bf7-389d21072d13" type="video/mp4"> </video>
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nocobase/cache | AI (dependencies): Sibling monorepo package pinned to the same version; expected pattern for @nocobase/* releases. | ai | |
| dependencies | unvetted-dep:@nocobase/utils | AI (dependencies): Sibling monorepo package pinned to the same version; expected pattern for @nocobase/* releases. | ai | |
| dependencies | unvetted-dep:@nocobase/actions | AI (dependencies): Sibling monorepo package pinned to the same version; expected pattern for @nocobase/* releases. | ai | |
| dependencies | unvetted-dep:@nocobase/database | AI (dependencies): Sibling monorepo package pinned to the same version; expected pattern for @nocobase/* releases. | ai | |
| dependencies | unvetted-dep:@nocobase/resourcer | AI (dependencies): Sibling monorepo package pinned to the same version; expected pattern for @nocobase/* releases. | ai | |
| phantom-deps | phantom-dep:@nocobase/cache | AI (phantom-deps): Same-org sibling dep; indirect usage is normal in a monorepo context. | ai | |
| phantom-deps | phantom-dep:@types/jsonwebtoken | AI (phantom-deps): Type-only package; not directly imported at runtime but used for TypeScript type declarations. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README link dump is a false positive for NocoBase — a large OSS project with extensive documentation links. No keywords is minor and stable. | ai |
Versions (showing 6 of 109)
| Version | Deps | Published |
|---|---|---|
| 1.9.28 | 7 / 0 | |
| 1.9.27 | 7 / 0 | |
| 1.9.26 | 7 / 0 | |
| 1.9.25 | 7 / 0 | |
| 1.9.24 | 7 / 0 | |
| 1.9.23 | 7 / 0 |
v1.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.