@nocobase/plugin-auth
User authentication management, including password, SMS, and support for Single Sign-On (SSO) protocols, with extensibility.
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/client/d451b9556071e997.js | AI (source-diff): Standard webpack minified bundle for NocoBase plugin; exports named React components with NocoBase copyright header. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/bc33cbbb266ce917.js | AI (source-diff): Standard webpack minified bundle for NocoBase plugin; exports named React components with NocoBase copyright header. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/95a0e31032d919ee.js | AI (source-diff): Standard webpack minified bundle for NocoBase plugin; exports named React components with NocoBase copyright header. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/250783b43257256a.js | AI (source-diff): Standard webpack minified bundle for NocoBase plugin; exports named React components with NocoBase copyright header. Not malicious obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established NocoBase plugin package; no provenance attestation is consistent with all prior versions of this package family. | ai | |
| source-diff | obfuscated-file:dist/client/157.af5e16b0785736dd.js | AI (source-diff): Standard webpack-minified frontend bundle with NocoBase copyright header and recognizable React component exports. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/230.b77900c4ea335058.js | AI (source-diff): Standard webpack-minified frontend bundle with NocoBase copyright header and recognizable React component exports. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/678.681c3ad1b9542ad1.js | AI (source-diff): Standard webpack-minified frontend bundle with NocoBase copyright header and recognizable React component exports. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/757.16ac408237380d11.js | AI (source-diff): Standard webpack-minified frontend bundle with NocoBase copyright header and recognizable React component exports. Not malicious obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): NocoBase plugin packages link to official docs rather than embedding README content; this is consistent across the ecosystem and not indicative of spam. | ai | |
| source-diff | obfuscated-file:dist/client/8a134e884eae4f4b.js | AI (source-diff): Standard webpack-minified React UI bundle for NocoBase auth plugin. Content implements Authenticator management UI; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/client/85e4c2ae84e8063c.js | AI (source-diff): Standard webpack-minified React UI bundle for NocoBase auth plugin. Content implements sign-in/sign-up forms; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/client/367cf457dd5bebe5.js | AI (source-diff): Standard webpack-minified React UI bundle for NocoBase auth plugin. Content implements TokenPolicySettings component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/client/33daef301eb29bcf.js | AI (source-diff): Standard webpack-minified React UI bundle for NocoBase auth plugin. NocoBase ships all client code as webpack chunks; content is legitimate auth component code with NocoBase copyright header. | ai |
Versions (showing 25 of 126)
| Version | Deps | Published |
|---|---|---|
| 1.9.22 | 0 / 9 | |
| 1.9.21 | 0 / 9 | |
| 1.9.20 | 0 / 9 | |
| 1.9.19 | 0 / 9 | |
| 1.9.18 | 0 / 9 | |
| 1.9.17 | 0 / 9 | |
| 1.9.16 | 0 / 9 | |
| 1.9.15 | 0 / 9 | |
| 1.9.14 | 0 / 9 | |
| 1.9.13 | 0 / 9 | |
| 1.9.12 | 0 / 9 | |
| 1.9.11 | 0 / 9 | |
| 1.9.10 | 0 / 9 | |
| 1.9.9 | 0 / 9 | |
| 1.9.8 | 0 / 9 | |
| 1.9.7 | 0 / 9 | |
| 1.9.6 | 0 / 9 | |
| 1.9.5 | 0 / 9 | |
| 1.9.4 | 0 / 9 | |
| 1.9.3 | 0 / 9 | |
| 1.9.2 | 0 / 9 | |
| 1.9.1 | 0 / 9 | |
| 1.9.0 | 0 / 9 | |
| 1.8.33 | 0 / 9 | |
| 1.8.32 | 0 / 9 |
v1.9.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.