@oat-sa/tao-i18n-tools
Internationalisation tools for tao
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Known org (@oat-sa) team rotation, publisher matched to prior maintainer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal team churn for established org package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): minimatch is a benign, widely-used glob dependency. | ai | |
| dependencies | unvetted-dep:pofile | AI (dependencies): pofile is a stable, widely-used PO file parser; no known security issues and appropriate for this i18n tooling package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 7 / 5 | |
| 0.7.0 | 7 / 5 | |
| 0.6.0 | 6 / 5 | |
| 0.5.1 | 6 / 5 | |
| 0.5.0 | 6 / 5 | |
| 0.4.0 | 6 / 6 | |
| 0.3.0 | 6 / 6 | |
| 0.2.1 | 4 / 6 | |
| 0.2.0 | 4 / 6 | |
| 0.1.1 | 3 / 6 | |
| 0.1.0 | 3 / 6 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
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 (oat-admin) than the most recent previously approved version (anshul119) on 2024-04-04, but oat-admin 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.
v0.5.1
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 (oatymart) than the most recent previously approved version (anshul119) on 2024-04-02, but oatymart 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.
v0.5.0
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 (jsconan) than the most recent previously approved version (anshul119) on 2023-05-15, but jsconan 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.
v0.4.0
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 (oatymart) than the most recent previously approved version (anshul119) on 2022-08-22, but oatymart 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.
v0.3.0
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 (krampstudio) than the most recent previously approved version (anshul119) on 2021-08-12, but krampstudio 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.
v0.2.1
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 (krampstudio) than the most recent previously approved version (anshul119) on 2021-03-23, but krampstudio 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.
v0.2.0
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 (krampstudio) than the most recent previously approved version (anshul119) on 2020-06-15, but krampstudio 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.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.