@things-factory/env
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Declared in dependencies; used indirectly in build/config tooling. | ai | |
| phantom-deps | phantom-dep:loader-utils | AI (phantom-deps): Declared in dependencies; used indirectly in build/config tooling. | ai | |
| phantom-deps | phantom-dep:schema-utils | AI (phantom-deps): Declared in dependencies; used indirectly in build/config tooling. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require of package.json at app root is a documented config-loading pattern for this library; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @things-factory/env is a scoped package in an established monorepo; not a typosquat of ajv. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 9.2.33 | 6 / 0 | |
| 9.2.16 | 6 / 0 | |
| 9.2.13 | 6 / 0 | |
| 8.0.64 | 8 / 0 | |
| 6.4.10 | 8 / 0 | |
| 6.4.9 | 8 / 0 | |
| 4.3.767 | 8 / 0 | |
| 4.3.764 | 8 / 0 | |
| 4.3.755 | 8 / 0 | |
| 4.3.752 | 8 / 0 | |
| 4.3.749 | 8 / 0 | |
| 4.3.743 | 8 / 0 | |
| 4.3.740 | 8 / 0 | |
| 4.3.734 | 8 / 0 | |
| 4.3.729 | 8 / 0 | |
| 4.3.727 | 8 / 0 | |
| 4.3.725 | 8 / 0 | |
| 4.3.723 | 8 / 0 | |
| 4.3.721 | 8 / 0 | |
| 4.3.705 | 8 / 0 | |
| 4.3.704 | 8 / 0 | |
| 4.3.703 | 8 / 0 | |
| 4.3.591 | 8 / 0 | |
| 4.3.534 | 8 / 0 | |
| 4.3.526 | 8 / 0 |
v9.2.33
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2026-07-08, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.3.591
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.534
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.526
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.