← Home

@featurevisor/core

npm Repository Homepage

Core package of Featurevisor for Node.js usage

6
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

fahad19

Keywords

featurevisorfeaturefeaturesflagsfeature flagsfeature togglesfeature managementexperimentationexperimentexperiments

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package now publishes via GitHub Actions CI with SLSA attestation; this is the expected new publisher for the featurevisor monorepo. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped package @featurevisor/core is not a typosquat of cors; Levenshtein match is a false positive. ai
semgrep semgrep:dynamic-require AI (semgrep): Resolves sibling @featurevisor/cli package.json at runtime; benign build-tool pattern. ai
semgrep semgrep:child-process-import AI (semgrep): Build/CLI tool legitimately uses child_process for git operations; expected for this package type. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): 127.0.0.1 is localhost in a console.log for a local dev server; not a network exfiltration risk. ai

Versions (showing 6 of 6)

Version Deps Published
2.26.1 8 / 0
2.8.0 8 / 2
2.3.2 8 / 2
2.3.1 8 / 2
2.0.2 8 / 2
2.0.0 8 / 2

v2.26.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@featurevisor/core' is 1 edit(s) away from popular package 'cors'.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.0

2 findings
HIGH Publisher changed: fahad19 → GitHub Actions (on 2026-02-08) provenance

This version was published by a different npm account than previous versions on 2026-02-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.2

1 finding
LOW No provenance attestation provenance

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

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

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

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