office-addin-project
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:office-addin-manifest | AI (phantom-deps): Referenced in config files as documented; stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI/build tool from Microsoft OfficeDev org; child_process use in manifest converter is expected and documented. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.0.10 | 7 / 13 | |
| 1.0.9 | 7 / 13 | |
| 1.0.8 | 7 / 13 | |
| 1.0.7 | 7 / 13 | |
| 1.0.6 | 7 / 13 | |
| 1.0.5 | 7 / 13 | |
| 1.0.4 | 7 / 14 | |
| 1.0.3 | 7 / 14 | |
| 1.0.2 | 7 / 14 | |
| 1.0.1 | 7 / 14 | |
| 1.0.0 | 7 / 14 |
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.