@enbox/auth
Headless authentication and identity management SDK for Enbox
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Localhost DWN server discovery, not remote exfil target. | ai | |
| dependencies | unvetted-dep:@enbox/agent | AI (dependencies): Same-org monorepo sibling package. | ai | |
| phantom-deps | phantom-dep:@enbox/dids | AI (phantom-deps): Same-org sibling, heuristic false positive. | ai | |
| source-diff | obfuscated-file:dist/browser.mjs | AI (source-diff): Bundled esbuild browser output, not true obfuscation; matches build:browser script. | ai | |
| dependencies | unvetted-dep:@enbox/connect | AI (dependencies): Same-org monorepo sibling package, consistent with other @enbox/* deps. | ai | |
| phantom-deps | phantom-dep:@enbox/crypto | AI (phantom-deps): Same-org scope, used indirectly via build externals. | ai |
Versions (showing 83 of 83)
| Version | Deps | Published |
|---|---|---|
| 0.6.80 | 8 / 5 | |
| 0.6.79 | 8 / 5 | |
| 0.6.78 | 8 / 5 | |
| 0.6.77 | 8 / 5 | |
| 0.6.76 | 8 / 5 | |
| 0.6.75 | 8 / 5 | |
| 0.6.74 | 8 / 5 | |
| 0.6.73 | 8 / 5 | |
| 0.6.72 | 8 / 5 | |
| 0.6.71 | 8 / 5 | |
| 0.6.70 | 8 / 5 | |
| 0.6.69 | 8 / 5 | |
| 0.6.68 | 8 / 5 | |
| 0.6.66 | 8 / 5 | |
| 0.6.65 | 8 / 5 | |
| 0.6.64 | 8 / 5 | |
| 0.6.63 | 8 / 5 | |
| 0.6.62 | 8 / 5 | |
| 0.6.61 | 7 / 5 | |
| 0.6.60 | 7 / 5 | |
| 0.6.59 | 7 / 5 | |
| 0.6.58 | 7 / 5 | |
| 0.6.57 | 7 / 5 | |
| 0.6.56 | 7 / 5 | |
| 0.6.55 | 7 / 5 | |
| 0.6.54 | 7 / 5 | |
| 0.6.53 | 7 / 5 | |
| 0.6.52 | 7 / 5 | |
| 0.6.51 | 7 / 5 | |
| 0.6.50 | 7 / 5 | |
| 0.6.49 | 7 / 5 | |
| 0.6.48 | 7 / 5 | |
| 0.6.47 | 7 / 5 | |
| 0.6.46 | 7 / 5 | |
| 0.6.45 | 7 / 5 | |
| 0.6.44 | 7 / 5 | |
| 0.6.43 | 7 / 5 | |
| 0.6.42 | 7 / 5 | |
| 0.6.41 | 7 / 5 | |
| 0.6.40 | 7 / 5 | |
| 0.6.39 | 7 / 5 | |
| 0.6.38 | 7 / 5 | |
| 0.6.37 | 7 / 5 | |
| 0.6.36 | 7 / 5 | |
| 0.6.35 | 7 / 5 | |
| 0.6.34 | 7 / 5 | |
| 0.6.33 | 7 / 5 | |
| 0.6.32 | 7 / 5 | |
| 0.6.31 | 7 / 5 | |
| 0.6.30 | 7 / 5 | |
| 0.6.29 | 7 / 5 | |
| 0.6.28 | 7 / 5 | |
| 0.6.27 | 7 / 5 | |
| 0.6.26 | 7 / 5 | |
| 0.6.25 | 7 / 5 | |
| 0.6.24 | 7 / 5 | |
| 0.6.23 | 7 / 5 | |
| 0.6.22 | 7 / 5 | |
| 0.6.21 | 7 / 5 | |
| 0.6.20 | 7 / 5 | |
| 0.6.19 | 7 / 5 | |
| 0.6.18 | 7 / 5 | |
| 0.6.17 | 7 / 5 | |
| 0.6.16 | 7 / 5 | |
| 0.6.15 | 7 / 5 | |
| 0.6.14 | 7 / 5 | |
| 0.6.13 | 7 / 5 | |
| 0.6.12 | 7 / 5 | |
| 0.6.11 | 7 / 5 | |
| 0.6.10 | 7 / 5 | |
| 0.6.9 | 7 / 5 | |
| 0.6.8 | 7 / 5 | |
| 0.6.7 | 7 / 5 | |
| 0.6.6 | 7 / 5 | |
| 0.6.5 | 7 / 5 | |
| 0.6.4 | 7 / 5 | |
| 0.6.3 | 7 / 5 | |
| 0.6.2 | 7 / 5 | |
| 0.6.1 | 7 / 5 | |
| 0.6.0 | 7 / 5 | |
| 0.5.0 | 5 / 3 | |
| 0.4.0 | 5 / 4 | |
| 0.3.1 | 5 / 4 |
v0.6.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.62
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.
v0.6.61
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.
v0.6.60
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.
v0.6.59
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.
v0.6.58
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.
v0.6.57
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.
v0.6.56
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.
v0.6.55
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.
v0.6.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.