npmpackage.info

Gathering detailed insights and metrics for @cocalc/next

@cocalc/next - 0.103.5 | npmpackage.info

@cocalc/next

CoCalc: Collaborative Calculation in the Cloud

0.103.5

1,222

NOASSERTION

TypeScript

107.10 MB

4.4

Installations

npm install @cocalc/next

Developer Guide

BETA

Typescript

No

Module System

CommonJS, ESM

Node Version

16.18.0

NPM Version

8.19.2 Pull Requests

Open

8

Total

2,815

Closed

294

Merged

2,513

Issues

Open

1,440

Total

5,507

Closed

4,067

Releases

Unable to fetch releases

Languages

TypeScript

Python

CoffeeScript

JavaScript

Sass

CSS

HTML

Shell

Jupyter Notebook

Stylus

Sage

TeX

TypeScript (88.59%)

Python (4.03%)

CoffeeScript (3.71%)

JavaScript (2.59%)

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,222 Stars

44,410 Commits

224 Forks

49 Watchers

2,051 Branches

51 Contributors

Updated on Jul 16, 2025

Maintainers

View All 51 Contributors

Package Meta Information

Latest Version

0.103.5

Package Id

@cocalc/next@0.103.5

Unpacked Size

107.10 MB

Size

50.09 MB

File Count

2,281

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

The Next.js Server

Upgrades

IMPORTANT: When upgrading the next package, always do this:

1npm install -E next@latest  # note the -E!

This ensures that the version of next on the build machine when making the npm package is the same as the version on the server when you deploy it! I've been bitten by messing this up multiple times. The problem is:

Upgrade next, e.g., to version 12.1.5, say, so it says ^12.1.5 in package.json
Build and deploy npm module using next 12.1.5.
Install it on the server a day later... and it goes BOOM and totally break!
Why? Because the server has next 12.1.6 installed, due to semver. However, and this is important, nextjs's build has absolutely no respect for semver.

Overview

This is a next.js app, which is used as part of CoCalc to provide the landing page and the share server.

To develop this, mostly just edit code here and it will automatically reload (hot module reloading) without you having to refresh the page. As long as you're not changing basic configuration, you don't have to restart the server.

You don't need to start your own nextjs server here -- the hub handles that. That said, you can, especially for debugging purposes -- see package.json .

The Landing Page

The landing page is pages/index.tsx.

The Share Server

The paths for the share server are in pages/share. Also see lib/share and components/share for code specific to the share server.

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

@cocalc/next

Installations

Developer Guide

No

CommonJS, ESM

16.18.0

8.19.2

Pull Requests

8

2,815

294

2,513

Issues

1,440

5,507

4,067

Releases

Unable to fetch releases

Languages

Developer

Download Statistics

GitHub Statistics

Maintainers

Package Meta Information

Total Downloads

NaN

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Dev Dependencies

The Next.js Server

Upgrades

Overview

The Landing Page

The Share Server

10

10

10

10

9

0

0

0

0

0

0

0

4.4

/10