@oat-sa/tao-release-notes
Extract release notes from a TAO extension
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Declared as runtime dep; used transitively via graphql-request or dynamically — stable false positive. | ai | |
| phantom-deps | phantom-dep:minimist | AI (phantom-deps): Declared as runtime dep; likely used in CLI tooling — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:octonode | AI (phantom-deps): Declared as runtime dep for GitHub API access — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:simple-git | AI (phantom-deps): Declared as runtime dep for git operations — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cross-spawn | AI (phantom-deps): Declared as runtime dep for cross-platform process spawning — stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 17 / 10 | |
| 1.1.0 | 15 / 12 | |
| 1.0.1 | 15 / 12 | |
| 1.0.0 | 15 / 12 |
v1.1.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 (krampstudio) on 2021-07-13, 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.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.