office-addin-manifest
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@microsoft/teams-manifest | AI (dependencies): Official Microsoft package, benign dependency for OfficeDev tooling. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package; provenance absence is consistent across all versions and not a risk signal here. | ai | |
| dependencies | unvetted-dep:office-addin-usage-data | AI (dependencies): office-addin-usage-data is a sibling package in the same OfficeDev/Office-Addin-Scripts monorepo; stable dependency across versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.1.6 | 9 / 17 | |
| 2.1.5 | 9 / 18 | |
| 2.1.4 | 9 / 18 | |
| 2.1.3 | 9 / 16 | |
| 2.1.2 | 9 / 16 | |
| 2.1.1 | 9 / 16 | |
| 2.1.0 | 9 / 16 | |
| 2.0.3 | 9 / 16 | |
| 2.0.2 | 9 / 16 | |
| 2.0.1 | 9 / 16 | |
| 2.0.0 | 9 / 16 |
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.