@bhsd/code-standard MIT 18 versions

@bhsd/code-standard

npm Homepage

[![npm version](https://badge.fury.io/js/@bhsd%2Fcode-standard.svg)](https://www.npmjs.com/package/@bhsd/code-standard) [![License](https://img.shields.io/badge/License-MIT-brightgreen.svg)](LICENSE)

18

Versions

MIT

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

bhsd

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): Config package; deps are referenced in config objects, not imported directly.	ai	2026/06/01
phantom-deps	phantom-dep:@typescript-eslint/parser	AI (phantom-deps): Parser referenced in ESLint config by name, not imported directly.	ai	2026/06/01
phantom-deps	phantom-dep:@stylistic/stylelint-plugin	AI (phantom-deps): Stylelint plugin referenced in config, not imported directly.	ai	2026/06/01
phantom-deps	phantom-dep:stylelint-config-recommended	AI (phantom-deps): Stylelint config extended by name, not imported directly.	ai	2026/06/01
phantom-deps	phantom-dep:stylelint-plugin-use-baseline	AI (phantom-deps): Stylelint plugin referenced in config, not imported directly.	ai	2026/06/01

Versions (showing 18 of 18)

Version	Deps	Published
2.6.2	18 / 1	2026-06-01
2.6.1	18 / 1	2026-05-31
2.6.0	18 / 1	2026-05-31
2.5.1	13 / 4	2026-05-25
2.5.0	13 / 4	2026-05-19
2.4.2	13 / 4	2026-05-06
2.4.1	13 / 4	2026-05-03
2.4.0	13 / 4	2026-05-02
2.3.0	12 / 4	2026-04-25
2.2.0	12 / 4	2026-04-05
2.1.1	12 / 4	2026-03-17
2.1.0	12 / 4	2026-02-23
2.0.1	12 / 4	2026-02-11
2.0.0	12 / 4	2026-01-31
1.4.0	12 / 4	2026-01-28
1.3.2	12 / 4	2025-11-13
1.3.1	12 / 4	2025-11-04
1.3.0	12 / 4	2025-11-02

v2.6.2

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.1

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.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.

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

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

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

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

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