← Home

@necto-react/popper

npm Repository Homepage

Necto's React library for positioning, popovers, tooltips, and floating elements.

33
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

botond-szabocorinvo-release-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@necto/types AI (phantom-deps): Workspace monorepo; internal deps declared but not directly imported is expected. ai
phantom-deps phantom-dep:@necto-react/types AI (phantom-deps): Workspace monorepo; internal deps declared but not directly imported is expected. ai
bogus-package bogus-package AI (bogus-package): Workspace package; minimal README and no external repo link are normal for internal monorepo modules. ai

Versions (showing 33 of 33)

Version Deps Published
0.10.13 9 / 0
0.10.12 9 / 0
0.10.11 9 / 0
0.10.10 9 / 0
0.10.9 9 / 0
0.10.7 9 / 0
0.10.6 9 / 0
0.10.5 9 / 0
0.10.4 9 / 0
0.10.3 9 / 0
0.10.2 9 / 0
0.10.1 9 / 0
0.10.0 9 / 6
0.9.1 9 / 6
0.9.0 9 / 6
0.8.1 9 / 6
0.8.0 9 / 6
0.7.0 9 / 6
0.6.0 7 / 6
0.5.2 7 / 6
0.5.1 7 / 6
0.3.12 6 / 6
0.3.11 6 / 6
0.3.10 6 / 6
0.3.9 6 / 6
0.3.8 6 / 6
0.3.7 6 / 6
0.3.6 6 / 6
0.3.5 6 / 6
0.3.4 6 / 6
0.3.3 6 / 6
0.3.0 6 / 6
0.2.0 6 / 6

v0.10.13

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.10.12

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.12

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

v0.3.10

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

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

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

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

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

v0.3.3

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