npmpackage.info

Gathering detailed insights and metrics for @cocalc/assets

@cocalc/assets - 1.10.1 | npmpackage.info

@cocalc/assets

CoCalc: Collaborative Calculation in the Cloud

1.10.1

1,221

NOASSERTION

TypeScript

10.77 MB

4.4

Installations

npm install @cocalc/assets

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

16.18.0

NPM Version

8.19.2 Pull Requests

Open

9

Total

2,809

Closed

292

Merged

2,508

Issues

Open

1,439

Total

5,506

Closed

4,067

Releases

Unable to fetch releases

Languages

TypeScript

Python

CoffeeScript

JavaScript

Sass

CSS

HTML

Shell

Jupyter Notebook

Stylus

Sage

TeX

TypeScript (88.63%)

Python (4.02%)

CoffeeScript (3.7%)

JavaScript (2.58%)

Sass (0.32%)

CSS (0.23%)

HTML (0.17%)

Shell (0.17%)

Jupyter Notebook (0.08%)

Stylus (0.04%)

Sage (0.03%)

TeX (0.02%)

Developer

sagemathinc

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

NOASSERTION License

1,221 Stars

44,328 Commits

224 Forks

49 Watchers

2,045 Branches

50 Contributors

Updated on Jul 13, 2025

Maintainers

View All 50 Contributors

Package Meta Information

Latest Version

1.10.1

Package Id

@cocalc/assets@1.10.1

Unpacked Size

10.77 MB

Size

6.37 MB

File Count

146

NPM Version

8.19.2

Node Version

16.18.0

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

typescript url-loader

Dev Dependencies

@cocalc/backend uglify-js

Static Webapp Assets

This code is part of https://github.com/sagemathinc/cocalc and isn't currently designed to be used standalone.

TODO: This module is called "assets" so you immediately think "I better not put things other than assets here", and usually "assets" refers to static assets in the context of web application.

This sub-directory contains assets (images, code, etc.) for the frontend and static pages.

Licensing

Compute Environment

Here is a description of two optional files describing the content of the computational environment (programming languages, libraries, ...)

Do this if you want to test rendering with the full production data for compute-*.json:

~/cocalc/src/packages/assets$ curl https://storage.googleapis.com/cocalc-compute-environment/compute-components.json > compute-components.json
~/cocalc/src/packages/assets$ curl https://storage.googleapis.com/cocalc-compute-environment/compute-inventory.json > compute-inventory.json

Do NOT commit this to the repo. It's unlikely you accidentally will, because neither file is in the cocalc git repo.

`compute-inventory.json`

This is the "ground truth" of what is installed in the environment. Layout:

{
 "language_exes":             map of a full executable path to this dictionary:
   {
   "path to executable":
     {
       "doc"   : documentation string
       "lang"  : language (python, R, ...)
       "name"  : Anaconda R
       "url"   : website
     },
   "another path to a language executable":
     { ... }
   }

For each such language and executable path:


  "language name" : e.g. "python"
    {
    "path to executable" : defined in the dictionary above
      {
        "library 1" : "version"
        "library 2" : "version"
        ...
      },
    "path to another executable of that language":
      { ... }
    },
  "another language":
    { ... }
  }
}

`compute-components.json`

This JSON dictionary contains descriptions of each library. It is hand curated or autogenerated from databases. Note, there can be several instances of the same library being installed in the inventory file, while this description file only lists it once.

{
 "language": {
   "library name": {
     "descr"        : "long description of the library",
     "doc"          : "documentation URL",
     "name"         : "Name",
     "summary"      : "short summary",
     "url"          : "website"
   },
   "library 2": { ... }
 },
 "another language" : { ... }
 "executables": {     # special language listing all executables with their full path
   "/bin/bash": {
     "name": "Bash",
     "..." : ...
   }, ...
 }

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Security-Policy

Determines if the project has published a security policy.

10

Maintained

Determines if the project is "actively maintained".

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

9

License

Determines if the project has defined a license.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

SAST

Determines if the project uses static code analysis.

0

Fuzzing

Determines if the project uses fuzzing.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

4.4

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More