← Home

@tour-kit/surveys

In-app microsurveys for React — NPS, CSAT, CES, and custom feedback flows with skip logic, audience targeting, fatigue prevention, sampling, and modal/slideout/banner/popover/inline display modes

16
Versions
SEE LICENSE IN LICENSE.md
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

domidex

Keywords

in-app-surveymicrosurveynpscsatcesnet-promoter-scorecustomer-feedbackuser-feedbackfeedback-widgetreact-surveyskip-logicaudience-targetingfatigue-preventiononboardingtour-kitdelighted-alternativesprig-alternativewootric-alternativetypeform-alternative

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@floating-ui/react AI (phantom-deps): Declared as a runtime dependency in the monorepo package; likely re-exported or used indirectly via bundled output. ai
phantom-deps phantom-dep:@radix-ui/react-slot AI (phantom-deps): Same pattern — declared runtime dep, used indirectly or re-exported in the bundle. ai
phantom-deps phantom-dep:@radix-ui/react-dialog AI (phantom-deps): Same pattern — declared runtime dep, used indirectly or re-exported in the bundle. ai

Versions (showing 16 of 16)

Version Deps Published
3.0.6 6 / 14
3.0.5 6 / 14
3.0.4 6 / 14
3.0.3 6 / 14
3.0.0 6 / 14
2.0.0 6 / 14
1.2.0 6 / 14
1.1.0 6 / 14
1.0.0 5 / 14
0.8.0 5 / 14
0.1.6 5 / 14
0.1.5 7 / 14
0.1.4 7 / 14
0.1.3 8 / 15
0.1.2 8 / 15
0.1.1 8 / 15

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

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

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