← Home

@builderbot/database-json

npm Repository Homepage

Esto es el conector a json

28
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

leifermendez

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; sparse README and no keywords are typical for internal connectors, not spam. ai
dependencies unvetted-dep:@builderbot/bot AI (dependencies): Sibling package in the same @builderbot monorepo; not an external unvetted dependency. ai

Versions (showing 28 of 28)

Version Deps Published
1.4.2 1 / 9
1.4.1 1 / 9
1.4.0 1 / 9
1.3.15 1 / 9
1.3.14 1 / 9
1.3.13 1 / 9
1.3.12 1 / 9
1.3.11 1 / 9
1.3.10 1 / 9
1.3.8 1 / 9
1.3.7 1 / 9
1.3.5 1 / 9
1.3.4 1 / 9
1.3.3 1 / 9
1.3.1 1 / 9
1.2.9 1 / 9
1.2.8 1 / 9
1.2.7 1 / 9
1.2.6 1 / 9
1.2.5 1 / 9
1.2.4 1 / 9
1.2.3 1 / 9
1.2.2 1 / 9
1.2.1 1 / 9
1.1.9 1 / 9
1.1.7 1 / 9
1.1.6 1 / 9
1.1.5 1 / 9

v1.2.5

1 finding
LOW No provenance attestation provenance

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

v1.2.4

1 finding
LOW No provenance attestation provenance

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

v1.2.3

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.1.9

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

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