← Home

@iyio/rtxt

npm
39
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

iyio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:zod AI (phantom-deps): Likely peer/config-level dependency in a monorepo context; stable false positive for this package. ai
phantom-deps phantom-dep:uuid AI (phantom-deps): Monorepo sub-package; phantom dep likely used via peer/shared resolution. ai
phantom-deps phantom-dep:date-fns AI (phantom-deps): Monorepo sub-package; phantom dep likely used via peer/shared resolution. ai
typosquat typosquat.levenshtein:next AI (typosquat): Scoped @iyio package in a large monorepo; not a typosquat of 'next'. ai
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped @iyio package in a large monorepo; not a typosquat of 'nuxt'. ai

Versions (showing 39 of 39)

Version Deps Published
0.9.1 0 / 0
0.8.18 0 / 0
0.8.17 0 / 0
0.8.11 0 / 0
0.8.1 0 / 0
0.8.0 0 / 0
0.7.50 3 / 0
0.7.43 3 / 0
0.7.42 3 / 0
0.7.37 3 / 0
0.7.36 3 / 0
0.7.34 3 / 0
0.7.33 3 / 0
0.7.31 3 / 0
0.7.29 3 / 0
0.7.28 3 / 0
0.7.24 3 / 0
0.7.23 4 / 0
0.7.22 4 / 0
0.7.19 4 / 0
0.7.17 4 / 0
0.7.15 4 / 0
0.7.14 4 / 0
0.7.13 4 / 0
0.7.12 4 / 0
0.7.11 4 / 0
0.7.10 4 / 0
0.7.9 4 / 0
0.7.7 4 / 0
0.7.6 4 / 0
0.7.5 4 / 0
0.7.2 4 / 0
0.7.0 4 / 0
0.6.5 4 / 0
0.6.4 4 / 0
0.6.3 4 / 0
0.6.0 4 / 0
0.5.18 4 / 0
0.5.17 4 / 0

v0.7.12

1 finding
LOW No provenance attestation provenance

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

v0.7.11

1 finding
LOW No provenance attestation provenance

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

v0.7.10

1 finding
LOW No provenance attestation provenance

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

v0.7.9

1 finding
LOW No provenance attestation provenance

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

v0.7.7

1 finding
LOW No provenance attestation provenance

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

v0.7.6

1 finding
LOW No provenance attestation provenance

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

v0.7.5

1 finding
LOW No provenance attestation provenance

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

v0.7.2

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.5

1 finding
LOW No provenance attestation provenance

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

v0.6.4

1 finding
LOW No provenance attestation provenance

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

v0.6.3

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.18

1 finding
LOW No provenance attestation provenance

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

v0.5.17

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.