← Home

@moneko/react

npm

react

11
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

moneko

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Scoped internal package with 105 published versions; sparse metadata is a stable characteristic, not a spam indicator. ai
phantom-deps phantom-dep:react-router AI (phantom-deps): Referenced in config files only; stable pattern for this build-tooling package. ai
phantom-deps phantom-dep:react-refresh AI (phantom-deps): Referenced in config files only; stable pattern for this build-tooling package. ai
phantom-deps phantom-dep:react-refresh-typescript AI (phantom-deps): Referenced in config files only; stable pattern for this build-tooling package. ai
phantom-deps phantom-dep:@pmmmwh/react-refresh-webpack-plugin AI (phantom-deps): Referenced in config files only; stable pattern for this build-tooling package. ai

Versions (showing 11 of 11)

Version Deps Published
3.0.7 6 / 8
3.0.6 6 / 8
3.0.5 6 / 8
3.0.4 6 / 8
3.0.3 6 / 8
3.0.2 6 / 8
3.0.1 6 / 8
3.0.0 6 / 8
2.2.1 6 / 14
2.2.0 6 / 14
2.1.6 6 / 14

v3.0.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.

v3.0.6

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.

v3.0.5

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.

v3.0.4

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.

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.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.

v3.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.

v2.2.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.

v2.2.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.

v2.1.6

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.