← Home

@hydrooj/framework

npm Repository
21
Versions
MIT
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.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; consistent with legitimate CI/CD migration for hydro-dev/Hydro. ai
publish-pattern new-deps-added AI (publish-pattern): @koa/router is a well-known Koa routing library; appropriate for a web framework package. ai
npm-metadata no-description AI (npm-metadata): Scoped package with valid repo URL and CI/CD provenance; missing description is benign. ai
dependencies unvetted-dep:@hydrooj/utils AI (dependencies): Sibling package in the same hydro-dev/Hydro monorepo; stable false positive for this package. ai
dependencies unvetted-dep:shorty.js AI (dependencies): Legitimate utility dependency used by the Hydro project; no malicious indicators. ai

Versions (showing 21 of 21)

Version Deps Published
0.3.0 13 / 5
0.2.7 13 / 5
0.2.6 13 / 5
0.2.4 13 / 6
0.2.3 13 / 6
0.2.2 13 / 6
0.2.1 13 / 6
0.2.0 13 / 6
0.1.5 14 / 7
0.1.4 14 / 7
0.1.3 14 / 7
0.1.2 14 / 7
0.1.1 14 / 7
0.1.0 14 / 7
0.0.7 14 / 7
0.0.6 14 / 7
0.0.5 14 / 7
0.0.4 14 / 7
0.0.3 14 / 7
0.0.2 14 / 7
0.0.1 14 / 7

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

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. Consider requesting the maintainer enable provenance via CI/CD.

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.