← Home

@buoy-gg/debug-borders

npm Repository Homepage

debug-borders package

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

Keywords

react-nativeexpodevtoolsdebuggingreact-native-devtoolsflipper-alternativelayout-debuggingbordersui-debugging

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 versions. ai
provenance no-provenance AI (provenance): Provenance absence is common; no other risk signals present for this package. ai

Versions (showing 34 of 34)

Version Deps Published
7.0.4 2 / 4
7.0.3 2 / 4
7.0.2 2 / 4
7.0.1 2 / 4
7.0.0 2 / 4
6.0.1 2 / 4
6.0.0 2 / 4
5.0.0 2 / 4
4.0.2 2 / 4
4.0.1 2 / 4
3.0.2 2 / 4
3.0.1 2 / 4
3.0.0 2 / 4
2.1.16 2 / 4
2.1.15 2 / 4
2.1.14 2 / 4
2.1.13 2 / 4
2.1.12 2 / 4
2.1.11 2 / 4
2.1.10 2 / 4
2.1.9 2 / 4
2.1.8 2 / 4
2.1.6 2 / 4
2.1.5 2 / 4
2.1.4 2 / 4
2.1.3 2 / 4
2.1.2 2 / 4
2.1.1 2 / 4
2.0.9 2 / 4
2.0.8 2 / 3
2.0.5 2 / 3
2.0.4 2 / 3
2.0.3 2 / 3
2.0.2 2 / 3

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.