@agentuity/config
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
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.1.13 | 1 / 2 | |
| 3.1.12 | 1 / 2 | |
| 3.1.11 | 1 / 2 | |
| 3.1.10 | 1 / 2 | |
| 3.1.9 | 1 / 2 | |
| 3.1.8 | 1 / 2 | |
| 3.1.7 | 1 / 2 | |
| 3.1.6 | 1 / 2 | |
| 3.1.5 | 1 / 2 | |
| 3.1.4 | 1 / 2 | |
| 3.1.3 | 1 / 2 | |
| 3.1.2 | 1 / 2 | |
| 3.1.1 | 1 / 2 | |
| 3.1.0 | 1 / 2 |
v3.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
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 (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-20, but jhaynie 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.
v3.1.9
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 (huijiro) than the most recent previously approved version (jhaynie) on 2026-07-08, but huijiro 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.
v3.1.8
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 (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-06, but jhaynie 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.
v3.1.7
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 (huijiro) than the most recent previously approved version (jhaynie) on 2026-07-03, but huijiro 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.
v3.1.6
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 (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-02, but jhaynie 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.
v3.1.5
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 (huijiro) than the most recent previously approved version (jhaynie) on 2026-06-29, but huijiro 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.