← Home

@miurajs/miura-router

npm
21
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

fernando_alves

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Part of a versioned monorepo; 0.0.0 is the initial placeholder, not a throwaway malicious package. ai
phantom-deps phantom-dep:@miura/miura-debugger AI (phantom-deps): workspace:* dep is a monorepo artifact; not expected to be directly imported in published code. ai
dependencies unvetted-dep:@miura/miura-debugger AI (dependencies): workspace:* constraint is a monorepo internal dep; won't resolve as an external npm dependency. ai

Versions (showing 21 of 21)

Version Deps Published
0.4.7 1 / 1
0.4.5 1 / 1
0.4.4 1 / 1
0.4.3 1 / 1
0.4.2 1 / 1
0.4.1 1 / 1
0.4.0 1 / 1
0.3.5 1 / 1
0.3.4 1 / 1
0.3.3 1 / 1
0.3.2 1 / 1
0.3.1 1 / 1
0.3.0 1 / 1
0.1.7 1 / 1
0.1.6 1 / 1
0.1.5 1 / 1
0.1.4 1 / 1
0.1.2 1 / 1
0.1.1 1 / 1
0.1.0 1 / 1
0.0.0 1 / 1

v0.4.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.

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

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.

v0.0.0

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.