← Home

@enbox/browser

npm Repository Homepage

Enbox tools and features to use in the browser

100
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

itsliran

Keywords

decentralizeddecentralized-applicationsdecentralized-identitydecentralized-webDIDsdkverifiable-credentialsweb5web5-sdkbrowsertools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Feature-detection shim for import.meta, no external input executed. ai
source-diff obfuscated-file:dist/browser.mjs AI (source-diff): Minified bundler output with sourcemap, not true obfuscation; behavior matches package's DID/DWN purpose. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are first-party @enbox/* monorepo siblings, not unknown third parties. ai
phantom-deps phantom-dep:@enbox/common AI (phantom-deps): Used via browser bundle externals, same-org sibling package. ai

Versions (showing 100 of 100)

Version Deps Published
0.3.65 9 / 9
0.3.64 9 / 9
0.3.63 9 / 9
0.3.62 9 / 9
0.3.61 9 / 9
0.3.60 9 / 9
0.3.59 9 / 9
0.3.58 9 / 9
0.3.57 8 / 9
0.3.56 8 / 9
0.3.55 8 / 9
0.3.54 8 / 9
0.3.53 8 / 9
0.3.52 8 / 9
0.3.51 8 / 9
0.3.49 8 / 9
0.3.48 8 / 9
0.3.47 8 / 9
0.3.46 8 / 9
0.3.45 8 / 9
0.3.44 8 / 9
0.3.43 8 / 7
0.3.42 7 / 7
0.3.41 7 / 7
0.3.40 7 / 7
0.3.39 4 / 7
0.3.38 4 / 7
0.3.37 4 / 7
0.3.36 4 / 7
0.3.35 4 / 7
0.3.34 4 / 7
0.3.33 4 / 7
0.3.32 4 / 7
0.3.31 4 / 7
0.3.30 4 / 7
0.3.29 4 / 7
0.3.28 4 / 7
0.3.27 4 / 7
0.3.26 4 / 7
0.3.25 4 / 7
0.3.24 4 / 7
0.3.23 4 / 7
0.3.22 4 / 7
0.3.21 4 / 7
0.3.20 4 / 7
0.3.19 4 / 7
0.3.18 4 / 7
0.3.17 4 / 7
0.3.16 4 / 7
0.3.15 4 / 7
0.3.14 4 / 7
0.3.13 4 / 7
0.3.12 4 / 7
0.3.11 4 / 7
0.3.10 4 / 7
0.3.9 4 / 7
0.3.8 4 / 7
0.3.7 4 / 7
0.3.6 4 / 7
0.3.5 4 / 7
0.3.4 4 / 7
0.3.3 4 / 7
0.3.2 4 / 7
0.3.1 4 / 7
0.3.0 4 / 7
0.2.1 3 / 7
0.2.0 3 / 7
0.1.26 3 / 7
0.1.25 3 / 7
0.1.24 3 / 7
0.1.23 3 / 7
0.1.22 3 / 7
0.1.21 3 / 7
0.1.20 3 / 7
0.1.19 3 / 7
0.1.18 3 / 7
0.1.17 3 / 7
0.1.16 3 / 7
0.1.15 3 / 7
0.1.14 3 / 7
0.1.13 3 / 7
0.1.12 3 / 7
0.1.11 3 / 7
0.1.10 3 / 7
0.1.9 3 / 7
0.1.8 3 / 7
0.1.7 3 / 7
0.1.6 3 / 7
0.1.5 3 / 7
0.1.4 3 / 7
0.1.3 1 / 7
0.1.2 1 / 8
0.1.1 1 / 8
0.1.0 1 / 8
0.0.6 1 / 8
0.0.5 1 / 8
0.0.4 1 / 8
0.0.3 1 / 19
0.0.2 1 / 21
0.0.1 1 / 21

v0.3.65

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.64

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.63

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.62

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.61

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.60

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.58

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.57

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.56

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.55

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.54

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.53

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.52

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.51

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.49

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.48

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.46

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.43

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.42

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.41

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.40

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.39

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.38

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.37

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.36

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.35

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.34

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.33

2 findings
HIGH New obfuscated file: dist/browser.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.