← Home

@stdlib/error-tools-fmtprodmsg

npm Repository Homepage

Format an error message for production.

8
Versions
Apache-2.0
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

stdlib-botkgryteplaneshifterrreusser

Keywords

stdlibstdutilsstdutilutilsutilutilitiesutilityerrorerrmessagemsgformatfmtminifyminification

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Common across npm; not a specific risk signal for this trusted package. ai
phantom-deps phantom-dep:@stdlib/types AI (phantom-deps): Same-org stdlib type dep, common pattern across stdlib packages. ai
npm-metadata url-dep:tape AI (npm-metadata): Dev-only test dep pinned to a fork branch; no runtime impact. ai

Versions (showing 8 of 8)

Version Deps Published
0.2.3 0 / 0
0.2.2 0 / 0
0.2.1 0 / 0
0.2.0 1 / 3
0.1.1 1 / 3
0.1.0 1 / 3
0.0.2 1 / 3
0.0.1 7 / 3

v0.2.2

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.

v0.2.1

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.

v0.2.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.

v0.1.1

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.

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

v0.0.2

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.

v0.0.1

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.