@hydrooj/vjudge AGPL-3.0-or-later 11 versions

@hydrooj/vjudge

npm Repository

Submit problems to remote oj

11

Versions

AGPL-3.0-or-later

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pandadtdyyundefinedmoe

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
license	copyleft-license:AGPL-3.0-or-later	AI (license): AGPL-3.0 is the declared license for the entire Hydro project; stable across all versions.	ai	2026/05/05

Versions (showing 11 of 11)

Version	Deps	Published
1.10.0	4 / 2	2026-04-30
1.9.16	4 / 2	2025-01-21
1.9.15	4 / 2	2024-12-14
1.9.14	4 / 2	2024-11-05
1.9.13	4 / 2	2024-10-23
1.9.12	4 / 2	2024-10-06
1.9.11	4 / 2	2024-09-19
1.9.10	4 / 2	2024-08-10
1.9.9	4 / 2	2024-08-03
1.9.8	4 / 2	2024-07-15
1.9.7	4 / 2	2024-05-10

v1.9.16

1 finding

LOW No provenance attestation provenance

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

v1.9.15

1 finding

LOW No provenance attestation provenance

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

v1.9.14

1 finding

LOW No provenance attestation provenance

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

v1.9.13

1 finding

LOW No provenance attestation provenance

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

v1.9.12

1 finding

LOW No provenance attestation provenance

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

v1.9.11

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.

v1.9.10

1 finding

LOW No provenance attestation provenance

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

v1.9.9

1 finding

LOW No provenance attestation provenance

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

v1.9.8

1 finding

LOW No provenance attestation provenance

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

v1.9.7

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.