← Home

@blumintinc/eslint-plugin-blumint

npm Repository Homepage

Custom eslint rules for use within BluMint

14
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

oconnorjosephjavier.blumint

Keywords

eslinteslintplugineslint-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:@blumintinc/eslint-plugin-blumint AI (npm-metadata): Self-referential file: dep for local dev/testing of the plugin itself, not external code. ai
phantom-deps phantom-dep:reflect-metadata AI (phantom-deps): Known implicit runtime dependency. ai
phantom-deps phantom-dep:typescript-memoize AI (phantom-deps): Used via config/decorators, not direct import. ai
phantom-deps phantom-dep:minimatch AI (phantom-deps): Used in config/glob matching, not a direct import concern. ai
phantom-deps phantom-dep:requireindex AI (phantom-deps): Long-standing convention-based loader dep for this plugin. ai
phantom-deps phantom-dep:@types/pluralize AI (phantom-deps): Type-only dependency, expected to be unimported directly. ai

Versions (showing 14 of 114)

Version Deps Published
1.1.9 1 / 44
1.1.8 1 / 44
1.1.7 1 / 44
1.1.6 1 / 44
1.1.5 1 / 41
1.1.4 1 / 41
1.1.3 1 / 41
1.1.2 1 / 41
1.1.1 1 / 41
1.1.0 1 / 41
1.0.5 1 / 41
1.0.4 1 / 41
1.0.3 1 / 41
1.0.2 2 / 36

v1.1.9

1 finding
LOW No provenance attestation provenance

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

v1.1.8

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

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

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