← Home

@servicetitan/form

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

st-teamrgdelatojesspkarpoffseanmadidextersealy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped @servicetitan org package with 342 versions; Levenshtein match to 'cors' is a false positive. ai

Versions (showing 33 of 33)

Version Deps Published
41.2.0 5 / 23
41.1.0 5 / 23
41.0.0 5 / 23
40.3.0 5 / 23
40.2.0 5 / 23
40.1.0 5 / 23
40.0.0 5 / 23
39.3.1 5 / 23
39.3.0 5 / 23
39.2.0 5 / 23
39.1.0 5 / 23
39.0.0 5 / 23
38.7.0 5 / 23
38.6.1 5 / 23
38.6.0 5 / 21
38.5.0 5 / 21
38.4.1 5 / 21
38.4.0 5 / 21
38.3.2 5 / 21
38.3.1 5 / 21
38.3.0 5 / 21
38.2.0 5 / 20
38.1.0 5 / 20
38.0.0 5 / 20
37.0.3 5 / 20
37.0.2 5 / 20
37.0.1 5 / 20
37.0.0 5 / 20
36.0.0 5 / 20
35.1.0 5 / 20
35.0.0 4 / 19
34.0.0 4 / 19
33.0.0 4 / 19

v41.2.0

1 finding
LOW No provenance attestation provenance

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

v41.1.0

1 finding
LOW No provenance attestation provenance

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

v41.0.0

1 finding
LOW No provenance attestation provenance

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

v40.3.0

1 finding
LOW No provenance attestation provenance

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

v40.2.0

1 finding
LOW No provenance attestation provenance

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