← Home

@highflame/policy

npm Repository Homepage
51
Versions
—
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

akhiljavelinakashjavelinsharathrajasekar

Keywords

cedarpolicyauthorizationhighflame

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions bot is a standard CI/CD automation pattern, not a compromise indicator. ai
source-diff obfuscated-file:dist/service-schemas.gen.d.ts AI (source-diff): Long lines are an embedded Cedar schema string constant in a .d.ts file, not obfuscated malicious code. ai
semgrep semgrep:etc-passwd-access AI (semgrep): Appears only in test fixtures as a string literal for Cedar policy evaluation; not executable credential access. ai

Versions (showing 51 of 57)

View all versions
Version Deps Published
2.1.43 1 / 3
2.1.42 1 / 3
2.1.41 1 / 3
2.1.40 1 / 3
2.1.39 1 / 3
2.1.38 1 / 3
2.1.37 1 / 3
2.1.36 1 / 3
2.1.35 1 / 3
2.1.34 1 / 3
2.1.33 1 / 3
2.1.32 1 / 3
2.1.31 1 / 3
2.1.30 1 / 3
2.1.29 1 / 3
2.1.28 1 / 3
2.1.26 1 / 3
2.1.25 1 / 3
2.1.24 1 / 3
2.1.23 1 / 3
2.1.22 1 / 3
2.1.21 1 / 3
2.1.20 1 / 3
2.1.19 1 / 3
2.1.18 1 / 3
2.1.17 1 / 3
2.1.16 1 / 3
2.1.15 1 / 3
2.1.14 1 / 3
2.1.13 1 / 3
2.1.12 1 / 3
2.1.11 1 / 3
2.1.10 1 / 3
2.1.9 1 / 3
2.1.8 1 / 3
2.1.7 1 / 3
2.1.6 1 / 3
2.1.5 1 / 3
2.1.4 1 / 3
2.1.3 1 / 3
2.1.2 1 / 3
2.1.1 1 / 3
2.1.0 1 / 3
2.0.10 1 / 3
2.0.9 1 / 3
2.0.8 1 / 3
2.0.7 1 / 3
2.0.6 1 / 3
2.0.5 1 / 3
2.0.4 1 / 3
2.0.3 1 / 3

v2.1.43

1 finding
LOW No provenance attestation provenance

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

v2.1.42

1 finding
LOW No provenance attestation provenance

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

v2.1.41

1 finding
LOW No provenance attestation provenance

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

v2.1.40

1 finding
LOW No provenance attestation provenance

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

v2.1.39

2 findings
HIGH Publisher changed: akhiljavelin → GitHub Actions (on 2026-05-25) provenance

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

LOW No provenance attestation provenance

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

v2.1.38

2 findings
HIGH Publisher changed: akhiljavelin → GitHub Actions (on 2026-05-22) provenance

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

LOW No provenance attestation provenance

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

v2.1.37

1 finding
LOW No provenance attestation provenance

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

v2.1.36

1 finding
LOW No provenance attestation provenance

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

v2.1.35

1 finding
LOW No provenance attestation provenance

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

v2.1.34

1 finding
LOW No provenance attestation provenance

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

v2.1.33

1 finding
LOW No provenance attestation provenance

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

v2.1.32

1 finding
LOW No provenance attestation provenance

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

v2.1.31

1 finding
LOW No provenance attestation provenance

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

v2.1.29

1 finding
LOW No provenance attestation provenance

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

v2.1.28

1 finding
LOW No provenance attestation provenance

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

v2.1.26

1 finding
LOW No provenance attestation provenance

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

v2.1.25

1 finding
LOW No provenance attestation provenance

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

v2.1.24

1 finding
LOW No provenance attestation provenance

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

v2.1.23

1 finding
LOW No provenance attestation provenance

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

v2.1.22

1 finding
LOW No provenance attestation provenance

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

v2.1.21

1 finding
LOW No provenance attestation provenance

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

v2.1.20

1 finding
LOW No provenance attestation provenance

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

v2.1.19

1 finding
LOW No provenance attestation provenance

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

v2.1.18

1 finding
LOW No provenance attestation provenance

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

v2.1.17

1 finding
LOW No provenance attestation provenance

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

v2.1.16

1 finding
LOW No provenance attestation provenance

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

v2.1.15

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

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

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

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.11

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.10

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.9

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.8

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.7

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.6

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.5

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.4

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.3

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.2

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.1

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.0

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.10

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.9

2 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.8

4 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH etc-passwd-access: src/schemas.test.ts:398 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/b2897393fd29bca8d59ef33823296d92f02ad651/src/schemas.test.ts#L398 396 | resource: newEntityUID('Overwatch::Tool', 'shell'), 397 | context: { > 398 | content: 'cat /etc/passwd', 399 | source: 'claudecode', 400 | event: 'PreToolUse',

HIGH etc-passwd-access: src/schemas.test.ts:405 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/b2897393fd29bca8d59ef33823296d92f02ad651/src/schemas.test.ts#L405 403 | mcp_server: 'filesystem', 404 | mcp_tool: 'shell', > 405 | path: '/etc/passwd', 406 | cwd: '/workspace', 407 | workspace_root: '/workspace',

LOW No provenance attestation provenance

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

v2.0.7

4 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH etc-passwd-access: src/schemas.test.ts:382 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/f50ac841772085ae5a386025c90c7671ad93124c/src/schemas.test.ts#L382 380 | resource: newEntityUID('Overwatch::Tool', 'shell'), 381 | context: { > 382 | content: 'cat /etc/passwd', 383 | source: 'claudecode', 384 | event: 'PreToolUse',

HIGH etc-passwd-access: src/schemas.test.ts:389 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/f50ac841772085ae5a386025c90c7671ad93124c/src/schemas.test.ts#L389 387 | mcp_server: 'filesystem', 388 | mcp_tool: 'shell', > 389 | path: '/etc/passwd', 390 | cwd: '/workspace', 391 | workspace_root: '/workspace',

LOW No provenance attestation provenance

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

v2.0.6

4 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH etc-passwd-access: src/schemas.test.ts:382 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/ca4cd9f3d1255603389ddf6442b83ae9cedab575/src/schemas.test.ts#L382 380 | resource: newEntityUID('Overwatch::Tool', 'shell'), 381 | context: { > 382 | content: 'cat /etc/passwd', 383 | source: 'claudecode', 384 | event: 'PreToolUse',

HIGH etc-passwd-access: src/schemas.test.ts:389 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/ca4cd9f3d1255603389ddf6442b83ae9cedab575/src/schemas.test.ts#L389 387 | mcp_server: 'filesystem', 388 | mcp_tool: 'shell', > 389 | path: '/etc/passwd', 390 | cwd: '/workspace', 391 | workspace_root: '/workspace',

LOW No provenance attestation provenance

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

v2.0.5

4 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH etc-passwd-access: src/schemas.test.ts:382 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/073513af3f45a57588383c2d1d10545f22a7d14b/src/schemas.test.ts#L382 380 | resource: newEntityUID('Overwatch::Tool', 'shell'), 381 | context: { > 382 | content: 'cat /etc/passwd', 383 | source: 'claudecode', 384 | event: 'PreToolUse',

HIGH etc-passwd-access: src/schemas.test.ts:389 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/073513af3f45a57588383c2d1d10545f22a7d14b/src/schemas.test.ts#L389 387 | mcp_server: 'filesystem', 388 | mcp_tool: 'shell', > 389 | path: '/etc/passwd', 390 | cwd: '/workspace', 391 | workspace_root: '/workspace',

LOW No provenance attestation provenance

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

v2.0.4

4 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH etc-passwd-access: src/schemas.test.ts:382 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/9e27ad01087a001b084d58835ad97f479ff39986/src/schemas.test.ts#L382 380 | resource: newEntityUID('Overwatch::Tool', 'shell'), 381 | context: { > 382 | content: 'cat /etc/passwd', 383 | source: 'claudecode', 384 | event: 'PreToolUse',

HIGH etc-passwd-access: src/schemas.test.ts:389 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/9e27ad01087a001b084d58835ad97f479ff39986/src/schemas.test.ts#L389 387 | mcp_server: 'filesystem', 388 | mcp_tool: 'shell', > 389 | path: '/etc/passwd', 390 | cwd: '/workspace', 391 | workspace_root: '/workspace',

LOW No provenance attestation provenance

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

v2.0.3

4 findings
HIGH New obfuscated file: dist/service-schemas.gen.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH etc-passwd-access: src/schemas.test.ts:382 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/7eb4d8f4e2bf9b0362b1402e0ee3d4053c8013df/src/schemas.test.ts#L382 380 | resource: newEntityUID('Overwatch::Tool', 'shell'), 381 | context: { > 382 | content: 'cat /etc/passwd', 383 | source: 'claudecode', 384 | event: 'PreToolUse',

HIGH etc-passwd-access: src/schemas.test.ts:389 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/highflame-ai/highflame-policy/blob/7eb4d8f4e2bf9b0362b1402e0ee3d4053c8013df/src/schemas.test.ts#L389 387 | mcp_server: 'filesystem', 388 | mcp_tool: 'shell', > 389 | path: '/etc/passwd', 390 | cwd: '/workspace', 391 | workspace_root: '/workspace',

LOW No provenance attestation provenance

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