← Home

@voiceflow/verror

npm Repository Homepage

xtrct.io error class

3
Versions
MIT
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

pmvrmcamandasteinhauerandrewlawrencetylerhhaneffervescentiajosh_vfvoiceflow-gallaganz4o4zsssoflyyyxavidopvf-serviceaccountzhilighttrsytolunsanasarjanjughazyanose-voiceflowdandonovan78theprofabuyakninabondarjbydeleychidi-voiceflowpateriackarjunsehgal-vfrohan-mandhotra-vfmackenzieleudevinabaghmar

Keywords

error

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Org-wide service-account migration, not a takeover pattern. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with prior maintainer set replaced by CI service account. ai
provenance publisher-changed-stale AI (provenance): Stale for 1391 days on npm, inconsistent with compromise. ai

Versions (showing 3 of 3)

Version Deps Published
1.1.6 1 / 20
1.1.1 1 / 20
1.1.0 1 / 13

v1.1.1

2 findings
MEDIUM Publisher changed: voiceflow-dev → vf-serviceaccount (on 2022-10-03, unremoved on npm for 1391d) provenance

This version was published by a different npm account (vf-serviceaccount) than the most recent previously approved version (voiceflow-dev) on 2022-10-03. It has since remained available on npm for 1391 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.1.0

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.