← Home

@checkstack/gitops-common

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

Maintainers

enyineer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:etc-passwd-access AI (semgrep): Fires in a test asserting path traversal to /etc/passwd returns null — defensive test, not credential harvesting. ai
bogus-package bogus-package AI (bogus-package): Scoped internal library under @checkstack org; missing metadata is typical for private/internal packages. ai
phantom-deps phantom-dep:@orpc/contract AI (phantom-deps): @orpc/contract is listed as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. ai

Versions (showing 11 of 11)

Version Deps Published
0.6.3 4 / 3
0.6.2 4 / 3
0.6.1 4 / 3
0.6.0 4 / 3
0.5.0 4 / 3
0.4.2 3 / 3
0.4.1 3 / 3
0.4.0 3 / 3
0.3.0 3 / 3
0.2.2 3 / 3
0.1.1 3 / 3

v0.6.3

1 finding
LOW No provenance attestation provenance

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

v0.6.2

1 finding
LOW No provenance attestation provenance

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

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

2 findings
HIGH etc-passwd-access: src/source-url.test.ts:118 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 116 | baseUrl: null, 117 | repository: "acme/checkstack", > 118 | filePath: "../etc/passwd", 119 | }), 120 | ).toBeNull();

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

2 findings
HIGH etc-passwd-access: src/source-url.test.ts:118 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 116 | baseUrl: null, 117 | repository: "acme/checkstack", > 118 | filePath: "../etc/passwd", 119 | }), 120 | ).toBeNull();

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