Skip to main content

@bureaudouble/context-session

Works with
JSR Score
29%

JSRScore

@bureaudouble/context-session
29%
The JSR score is a measure of the overall quality of a package, based on a number of factors such as documentation and runtime compatibility.
  • Has a readme or module doc

    The package should have a README.md in the root of the repository or a module doc in the main entrypoint of the package.

    0/2
  • Has examples in the readme or module doc

    The README or module doc of the main entrypoint should have an example of how to use the package, in the form of a code block.

    0/1
  • Has module docs in all entrypoints

    Every entrypoint of the package should have a module doc summarizing what is defined in that module.

    0/1
  • Has docs for most symbols

    At least 80% of the packages' symbols should have symbol documentation. Currently 0% of symbols are documented.

    0/5
  • No slow types are used

    The package should not use slow types.

    5/5
  • Has a description

    The package should have a description set in the package settings to help users find this package via search.

    0/1
  • At least one runtime is marked as compatible

    The package should be marked with at least one runtime as "compatible" in the package settings to aid users in understanding where they can use this package.

    0/1
  • At least two runtimes are marked as compatible

    The package should be compatible with more than one runtime, and be marked as such in the package settings.

    0/1
  • Has provenance

    The package should be published from a verifiable CI/CD workflow, and have a public transparency log entry.

    0/1