← Home

@buoy-gg/floating-tools-core

npm Repository Homepage

Headless core for floating tools - shared logic for web and React Native

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

Maintainers

lovesworking

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Likely local publish; no other risk signals present and package content is unchanged from prior approved version. ai
provenance no-provenance AI (provenance): Scoped org package without CI provenance; no other risk signals present. ai

Versions (showing 34 of 34)

Version Deps Published
7.0.4 0 / 3
7.0.3 0 / 3
7.0.2 0 / 3
7.0.1 0 / 3
7.0.0 0 / 3
6.0.1 0 / 3
6.0.0 0 / 3
5.0.0 0 / 3
4.0.2 0 / 3
4.0.1 0 / 3
3.0.2 0 / 3
3.0.1 0 / 3
3.0.0 0 / 3
2.2.0 0 / 3
2.1.15 0 / 3
2.1.14 0 / 3
2.1.13 0 / 3
2.1.12 0 / 3
2.1.11 0 / 3
2.1.10 0 / 3
2.1.9 0 / 3
2.1.8 0 / 3
2.1.6 0 / 3
2.1.5 0 / 3
2.1.4 0 / 3
2.1.3 0 / 3
2.1.2 0 / 3
2.1.1 0 / 3
1.7.8 0 / 3
1.7.7 0 / 3
1.7.5 0 / 2
1.7.4 0 / 2
1.7.3 0 / 2
1.7.2 0 / 2

v7.0.4

1 finding
INFO No provenance attestation provenance

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

v7.0.3

1 finding
INFO No provenance attestation provenance

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

v7.0.2

1 finding
INFO No provenance attestation provenance

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

v7.0.1

1 finding
INFO No provenance attestation provenance

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

v7.0.0

1 finding
INFO No provenance attestation provenance

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

v6.0.1

1 finding
INFO No provenance attestation provenance

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

v6.0.0

1 finding
INFO No provenance attestation provenance

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

v5.0.0

1 finding
INFO No provenance attestation provenance

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

v4.0.2

1 finding
INFO No provenance attestation provenance

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

v4.0.1

1 finding
INFO No provenance attestation provenance

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

v3.0.2

1 finding
INFO No provenance attestation provenance

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