← Home

@bpmnkit/api

9
Versions
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

urbanisierung

Keywords

camundazeebebpmnapiclientresttypescriptoauth2

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped BPMN/Camunda client; name similarity to hapi is coincidental substring match, not impersonation. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped BPMN/Camunda client; no relation to pg. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped BPMN/Camunda client; no relation to joi. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped BPMN/Camunda client; no relation to ajv. ai

Versions (showing 9 of 9)

Version Deps Published
0.0.18 0 / 0
0.0.17 0 / 0
0.0.16 0 / 0
0.0.13 0 / 0
0.0.12 0 / 0
0.0.11 0 / 0
0.0.10 0 / 0
0.0.9 0 / 0
0.0.8 0 / 0

v0.0.18

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@bpmnkit/api' is 1 edit(s) away from popular package 'hapi'.

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.