← Home

sdk-environment

npm Repository Homepage

parse and expose the environment your code runs in

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

uladkasach

Keywords

environmentconfigaccessservercommitruntime

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): Package grew from stub to full implementation; new files match stated AWS environment-detection purpose. ai
source-diff source-size-tripled AI (source-diff): Size increase reflects legitimate feature expansion from near-empty package to full implementation. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA attestation; legitimate automation handoff. ai
publish-pattern new-deps-added AI (publish-pattern): AWS SDK deps match package purpose (environment/config SDK); established AWS SDK packages. ai
phantom-deps phantom-dep:@noble/hashes AI (phantom-deps): Listed in both dependencies and devDependencies; config-file reference explains phantom-dep false positive. ai
phantom-deps phantom-dep:domain-glossaries AI (phantom-deps): Config-file reference pattern; stable false positive for this package. ai
phantom-deps phantom-dep:type-fns AI (phantom-deps): Dep appears in both dependencies and devDependencies; phantom-dep heuristic misfires on config-referenced packages. ai

Versions (showing 6 of 6)

Version Deps Published
0.1.5 4 / 36
0.1.3 4 / 35
0.1.2 2 / 35
0.1.1 2 / 35
0.1.0 1 / 35
0.0.0 3 / 37

v0.1.5

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

v0.1.3

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

v0.1.2

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

This version was published by a different npm account than previous versions on 2026-05-07. 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.

v0.1.1

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

This version was published by a different npm account than previous versions on 2026-05-06. 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.

v0.1.0

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

This version was published by a different npm account than previous versions on 2026-05-01. 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.

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